best solution for using a database and Java

[nunodonato]

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]

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!

nu********@gmail.com wrote:

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

[Lukas Weibel]

Hi,

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

Regards,
Lukas

nu********@gmail.com wrote:

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

[Alexandr Molochnikov]

Have a look at STEP FORWARD.

www.gestalt.com

<nu********@gmail.com> wrote in message
news:cd********@odak26.prod.google.com...

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

[Takeda]

Hi, there!

look for Pevayler. It is the answer for your questions.
nu********@gmail.com wrote in message news:<cd********@odak26.prod.google.com>...

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

[Christopher Browne]

Centuries ago, Nostradamus foresaw when David Morris <dm*****@dynamicquest.com> would write:

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.

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.gultn" "@" "enworbbc")
http://www3.sympatico.ca/cbbrowne/languages.html
Artificial intelligence, like fusion power, has been ten years away
for the last 30 years. -- Conrad Stack

[Nathan Zumwalt]

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 <cb******@acm.org> wrote in message news:<m3************@wolfe.cbbrowne.com>...

Centuries ago, Nostradamus foresaw when David Morris <dm*****@dynamicquest.com> would write:

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.

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.

[Christopher Browne]

After takin a swig o' Arrakan spice grog, na*****@hotmail.com (Nathan Zumwalt) belched out:

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.

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.

[Alex Molochnikov]

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 "aggregation" (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
www.gestalt.com

"Christopher Browne" <cb******@acm.org> wrote in message
news:m3************@wolfe.cbbrowne.com...

After takin a swig o' Arrakan spice grog, na*****@hotmail.com (Nathan

Zumwalt) belched out:

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.

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.