----- Original Message -----
From: "Jon Stevens" <[EMAIL PROTECTED]>
> Questions:
Thanks for the good questions (before too much code is written).
> #1. How are you going to handle the fact that every database out there has
a
> different set of needs for getting ID's for inserts?
We aren't using int IDs. Unique internal message IDs (strings) are already
getting created by the server (for the sake of locking and other reasons).
> #2. How are you going to handle the fact that every database out there has
a
> different idea of how SQL should be written?
Well, I haven't hit any issues yet... I've got an insert, 2 updates, 1
delete, and 2 selects... so far they're pretty straight forward. If I do
have to start jury-rigging something, then maybe Turbine is worth using.
For the time being, JDBC is actually doing a good job abstracting the
database.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
