Begining of Java Servlet Inteface
Mon, 14 May 2001 10:43:45 -0500

On 14 May 2001 11:32:23 EDT, the world broke into rejoicing as
Chris Shenton <>  said:
> writes:
> > I would suggest the thought that "multiuser" be considered completely
> > synonymous with "using SQL DBMS."  The database provides an interface
> > that supports many concurrent connections; that supports multiple
> > users without needing to think very much about it.

> Need to ensure the code to access the DB uses some kind of
> database-neutral API layer so we don't get locked into <insert your
> favorite DB>.  Would be nice if it could talk to MySQL, Postgres,
> Oracle, or whatever the user/customer has.

That's the point of the Java "java.sql.*" classes; if you have a JDBC
driver for the database in question, reconfiguring to use a different
database can be done at runtime.

   db = DriverManager.getConnection( "jdbc:postgresql:gnucash",
     "cbbrowne", password");

changes readily to:
   db = DriverManager.getConnection( "jdbc:mysql:mysql-gnucash",
     "cbbrowne", password");

I would thereby consider that "Servlet + JDBC" provides a direct
response to this issue to the effect that "Yup, that's already

> Also a DB doesn't necessarily shield you from multi-user,
> last-one-wins data corruption.  Without DB "transaction" support,
> there's no good way to have multiple people updating the same data
> and guarantee they won't step on each others toes.  You'd have to
> work around this for transaction-challanged DBs with extensive
> row/table locking.

Any of the databases worth considering offer transaction support.  It
seems not unreasonable to treat transactions as a must-have feature,
particularly when there are four "open source" databases offering

 - PostgreSQL
 - MySQL
 - Interbase

[I haven't successfully compiled SAPDB yet; seems to still need some
(reverse (concatenate 'string "gro.gultn@" "enworbbc"))
Is the surface of a planet the right place for an expanding
technological civilization?