Same Java SQL database engine on both client and server make more sense?
From: Phil Latio (phil.latio_at_f-in-stupid.co.uk)
Date: 07/29/04
- Previous message: Roedy Green: "Re: What about a new DB without SQL?"
- Next in thread: Roedy Green: "Re: Same Java SQL database engine on both client and server make more sense?"
- Reply: Roedy Green: "Re: Same Java SQL database engine on both client and server make more sense?"
- Reply: David Harper: "Re: Same Java SQL database engine on both client and server make more sense?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Jul 2004 03:24:10 GMT
I would like to hear opinions as I am venturing into the murky world of Java
databases for a project I wish to undertake.
Agents are wanting to use laptops to collect information. It's been decided
that they will need to go online twice a day and connect to a MySQL
database.
1. in the morning to download information regarding job instructions for the
day.
2. in the evening to upload the collected data.
My initial plan was to build a Java application for the agents laptops which
includes an embedded Java SQL database engine (such as HSQL, Mckoi, etc)
that communicates with MySQL. However I wonder if I have been looking at
this the wrong way and it make more sense to run the same Java SQL database
engine on both the agents laptops and the server (discarding MySQL on the
server).
Can anyone recommend a suitable database?
- Previous message: Roedy Green: "Re: What about a new DB without SQL?"
- Next in thread: Roedy Green: "Re: Same Java SQL database engine on both client and server make more sense?"
- Reply: Roedy Green: "Re: Same Java SQL database engine on both client and server make more sense?"
- Reply: David Harper: "Re: Same Java SQL database engine on both client and server make more sense?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
