best solution for using a database and Java

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • nunodonato@gmail.com

    best solution for using a database and Java

    hi there.
    i'm thinking of developing an app using Java to manage a library
    (books, clients, orders..etc).
    I am not sure of how to store the data, maybe using files or a DBMS.
    The ammount of data is probably not much to justify the use of a DBMS.
    I wanted to know your opinion, and how can i implement it?
    I've searched some JDBC drivers, but most of it are not free :( I found
    one free for MySQL.
    The disadvantages of using a DBMS is that i need to run a server, and
    this app only runs on one pc.. no need for network or anything.
    what do you think?

    thanks a lot

  • David Morris

    #2
    Re: best solution for using a database and Java

    If you want to use java as your development language, I would recommend
    MySQL as a cheap (free) but extremely powerfull database. And, as you
    have already discovered, it has a free JDBC driver already written. The
    AWT is very cumbersome in java however.

    Even though it is standalone. I would recommend writing in JSP on top
    of Tomcat. You would use your browser as the GUI component but java for
    all the backend processing. That is what I did for one of my
    applications and it works great.

    Also, if you ever want to access the application from outside, it would
    require minimal effort to do it.

    I hope this helps!

    nunodonato@gmai l.com wrote:[color=blue]
    > hi there.
    > i'm thinking of developing an app using Java to manage a library
    > (books, clients, orders..etc).
    > I am not sure of how to store the data, maybe using files or a DBMS.
    > The ammount of data is probably not much to justify the use of a DBMS.
    > I wanted to know your opinion, and how can i implement it?
    > I've searched some JDBC drivers, but most of it are not free :( I found
    > one free for MySQL.
    > The disadvantages of using a DBMS is that i need to run a server, and
    > this app only runs on one pc.. no need for network or anything.
    > what do you think?
    >
    > thanks a lot
    >[/color]


    Comment

    • Lukas Weibel

      #3
      Re: best solution for using a database and Java

      Hi,

      take a look at http://hsqldb.sourceforge.net/

      Regards,
      Lukas

      nunodonato@gmai l.com wrote:[color=blue]
      > hi there.
      > i'm thinking of developing an app using Java to manage a library
      > (books, clients, orders..etc).
      > I am not sure of how to store the data, maybe using files or a DBMS.
      > The ammount of data is probably not much to justify the use of a DBMS.
      > I wanted to know your opinion, and how can i implement it?
      > I've searched some JDBC drivers, but most of it are not free :( I found
      > one free for MySQL.
      > The disadvantages of using a DBMS is that i need to run a server, and
      > this app only runs on one pc.. no need for network or anything.
      > what do you think?
      >
      > thanks a lot
      >[/color]

      Comment

      • Alexandr Molochnikov

        #4
        Re: best solution for using a database and Java

        Have a look at STEP FORWARD.



        <nunodonato@gma il.com> wrote in message
        news:cd3n87$mi2 @odak26.prod.go ogle.com...[color=blue]
        > hi there.
        > i'm thinking of developing an app using Java to manage a library
        > (books, clients, orders..etc).
        > I am not sure of how to store the data, maybe using files or a DBMS.
        > The ammount of data is probably not much to justify the use of a DBMS.
        > I wanted to know your opinion, and how can i implement it?
        > I've searched some JDBC drivers, but most of it are not free :( I found
        > one free for MySQL.
        > The disadvantages of using a DBMS is that i need to run a server, and
        > this app only runs on one pc.. no need for network or anything.
        > what do you think?
        >
        > thanks a lot
        >[/color]


        Comment

        • Takeda

          #5
          Re: best solution for using a database and Java

          Hi, there!

          look for Pevayler. It is the answer for your questions.


          nunodonato@gmai l.com wrote in message news:<cd3n87$mi 2@odak26.prod.g oogle.com>...[color=blue]
          > hi there.
          > i'm thinking of developing an app using Java to manage a library
          > (books, clients, orders..etc).
          > I am not sure of how to store the data, maybe using files or a DBMS.
          > The ammount of data is probably not much to justify the use of a DBMS.
          > I wanted to know your opinion, and how can i implement it?
          > I've searched some JDBC drivers, but most of it are not free :( I found
          > one free for MySQL.
          > The disadvantages of using a DBMS is that i need to run a server, and
          > this app only runs on one pc.. no need for network or anything.
          > what do you think?
          >
          > thanks a lot[/color]

          Comment

          • Christopher Browne

            #6
            Re: best solution for using a database and Java

            Centuries ago, Nostradamus foresaw when David Morris <dmorris@dynami cquest.com> would write:[color=blue]
            > If you want to use java as your development language, I would
            > recommend MySQL as a cheap (free) but extremely powerfull database.
            > And, as you have already discovered, it has a free JDBC driver already
            > written. The AWT is very cumbersome in java however.[/color]

            Hmm? MySQL(tm) is only "free" if you plan to give away all of your
            code, licensing it under the GPL or some similar license. If you plan
            to connect anything to it that isn't "free software," it costs $450
            USD per server.
            --
            output = reverse("gro.gu ltn" "@" "enworbbc")

            Artificial intelligence, like fusion power, has been ten years away
            for the last 30 years. -- Conrad Stack

            Comment

            • Nathan Zumwalt

              #7
              Re: best solution for using a database and Java

              I see Bill and Steve are still trolling the newsgroups spreading FUD
              under assumed names.

              You're only required to GPL code if it is statically linked to the
              core MySQL engine (which is itself GPL'ed). If you're statically
              linking your web app to a database server, you've got bigger problems
              than the GPL.

              //Nathan

              Christopher Browne <cbbrowne@acm.o rg> wrote in message news:<m3llhmgem k.fsf@wolfe.cbb rowne.com>...[color=blue]
              > Centuries ago, Nostradamus foresaw when David Morris <dmorris@dynami cquest.com> would write:[color=green]
              > > If you want to use java as your development language, I would
              > > recommend MySQL as a cheap (free) but extremely powerfull database.
              > > And, as you have already discovered, it has a free JDBC driver already
              > > written. The AWT is very cumbersome in java however.[/color]
              >
              > Hmm? MySQL(tm) is only "free" if you plan to give away all of your
              > code, licensing it under the GPL or some similar license. If you plan
              > to connect anything to it that isn't "free software," it costs $450
              > USD per server.[/color]

              Comment

              • Christopher Browne

                #8
                Re: best solution for using a database and Java

                After takin a swig o' Arrakan spice grog, nathanz@hotmail .com (Nathan Zumwalt) belched out:[color=blue]
                > I see Bill and Steve are still trolling the newsgroups spreading FUD
                > under assumed names.
                >
                > You're only required to GPL code if it is statically linked to the
                > core MySQL engine (which is itself GPL'ed). If you're statically
                > linking your web app to a database server, you've got bigger problems
                > than the GPL.[/color]

                If that is your interpretation of MySQL AB's license, then I suggest
                you take that up with the vendor.

                <http://www.mysql.com/products/licensing/>

                At MySQL AB, we believe in open source / free software and we welcome
                all initiatives to publish more software under the GPL license, just
                as we have done.

                In their simplest form, the following are general licensing
                guidelines:

                * If your software is licensed under either the
                GPL-compatible Free Software License as defined by the Free
                Software Foundation or approved by OSI, then use our GPL
                licensed version.

                * If you distribute a proprietary application in any way, and you
                are not licensing and distributing your source code under GPL,
                you need to purchase a commercial license of MySQL

                * If you are unsure, we recommend that you buy our cost effective
                commercial licenses. That is the safest solution. Licensing
                questions can submitted online for our advice, and we encourage
                you to refer to the Free Software Foundation or a lawyer as
                appropriate.

                That set of "guidelines " doesn't say anything about static linking.
                It says that if the application is proprietary "in any way," then you
                have to pay.
                --
                let name="cbbrowne" and tld="ntlug.org" in name ^ "@" ^ tld;;

                On the other hand, you have different fingers.

                Comment

                • Alex Molochnikov

                  #9
                  Re: best solution for using a database and Java

                  I've had a discussion of this subject with MySQL Sales Manager. The bottom
                  line: if the application is not dependent on MySQL for its operation (e.g.
                  can work with some other RDBMS) and communicates with MySQL via a JDBC
                  driver (therefore, does not have static links to MySQL) then it does not
                  come under GPL. This is pretty much in line with the common interpretation
                  of GPL; the only difference being the "aggregatio n" (distribution of the
                  GPLed software with the non-GPLed product), which is specifically
                  permissible under the GPL, but not in MySQL's interpretation.

                  Alex Molochnikov
                  Gestalt Corporation


                  "Christophe r Browne" <cbbrowne@acm.o rg> wrote in message
                  news:m3n021eymo .fsf@wolfe.cbbr owne.com...[color=blue]
                  > After takin a swig o' Arrakan spice grog, nathanz@hotmail .com (Nathan[/color]
                  Zumwalt) belched out:[color=blue][color=green]
                  > > I see Bill and Steve are still trolling the newsgroups spreading FUD
                  > > under assumed names.
                  > >
                  > > You're only required to GPL code if it is statically linked to the
                  > > core MySQL engine (which is itself GPL'ed). If you're statically
                  > > linking your web app to a database server, you've got bigger problems
                  > > than the GPL.[/color]
                  >
                  > If that is your interpretation of MySQL AB's license, then I suggest
                  > you take that up with the vendor.
                  >
                  > <http://www.mysql.com/products/licensing/>
                  >
                  > At MySQL AB, we believe in open source / free software and we welcome
                  > all initiatives to publish more software under the GPL license, just
                  > as we have done.
                  >
                  > In their simplest form, the following are general licensing
                  > guidelines:
                  >
                  > * If your software is licensed under either the
                  > GPL-compatible Free Software License as defined by the Free
                  > Software Foundation or approved by OSI, then use our GPL
                  > licensed version.
                  >
                  > * If you distribute a proprietary application in any way, and you
                  > are not licensing and distributing your source code under GPL,
                  > you need to purchase a commercial license of MySQL
                  >
                  > * If you are unsure, we recommend that you buy our cost effective
                  > commercial licenses. That is the safest solution. Licensing
                  > questions can submitted online for our advice, and we encourage
                  > you to refer to the Free Software Foundation or a lawyer as
                  > appropriate.
                  >
                  > That set of "guidelines " doesn't say anything about static linking.
                  > It says that if the application is proprietary "in any way," then you
                  > have to pay.
                  > --
                  > let name="cbbrowne" and tld="ntlug.org" in name ^ "@" ^ tld;;
                  > http://www.ntlug.org/~cbbrowne/multiplexor.html
                  > On the other hand, you have different fingers.[/color]


                  Comment

                  Working...