Ben Pharr wrote:
> At 04:37 AM 8/8/00 , you wrote:
> >Whatever method is used, if every client needs its own copy, start-up
> >time is likely to be affected.
> >
> >If there is no central database presumably you don't want people to be
> >able to make changes which become available to other users
At 04:37 AM 8/8/00 , you wrote:
>Whatever method is used, if every client needs its own copy, start-up
>time is likely to be affected.
>
>If there is no central database presumably you don't want people to be
>able to make changes which become available to other users...
>
>What about using Object
Ben Pharr wrote:
> I would like to find a good way to store data for a Java program I'm
> writing. It is a LARGE amount of data, so parsing a text file at startup
> isn't an option. A database like MySQL isn't an option because of the
> problems of setting it up on each client. (This program n
You could try a pure Java DB, with a File-System Driver (Cloudscape
comes to mind). It does not require any DB to be started (i.e. no
network), and the JDBC drivers are type 4 (pure java).
-Larry
Ben Pharr wrote:
>
> I would like to find a good way to store data for a Java program I'm
> writ
Ben Pharr wrote:
> I would like to find a good way to store data for a Java program I'm
> writing. It is a LARGE amount of data, so parsing a text file at startup
> isn't an option.
Whatever method is used, if every client needs its own copy, start-up
time is likely to be affected.
> A data
I would like to find a good way to store data for a Java program I'm
writing. It is a LARGE amount of data, so parsing a text file at startup
isn't an option. A database like MySQL isn't an option because of the
problems of setting it up on each client. (This program needs to be able
to run
