> Christopher Browne <[EMAIL PROTECTED]> writes:
>
> > The options that leap to mind are:
>
> What did you think about the info I got on embedding MySQL and
> PosgreSQL (did I post that?).
I'm not sure I saw that; could be "user error" on my part.
> If not, I spoke to both camps, and the MySQL
> For example filling in a sequential primary
> key properly is a typical case, each database provides its own facility for,
> Oracle sequences, MSSQL identity columns, etc.
>
Just a note as a gainfully employed DBA:
_DO_NOT_USE_SEQUENTIALLY_INCREASING_COLUMNS_AS_PRIMARY_KEYS_
Please. Th
Christopher Browne <[EMAIL PROTECTED]> writes:
> The options that leap to mind are:
What did you think about the info I got on embedding MySQL and
PosgreSQL (did I post that?).
If not, I spoke to both camps, and the MySQL people said that they
already have a patch that'll allow embedded use. T
Christopher Browne wrote:
[...]
> The options that leap to mind are:
> a) Berkeley Sleepycat DB. This tends to be _included_ with GNU-related
>systems, and provides, in its latest versions, transaction logging,
>locking, and all that sort of thing. There has been some discussion
>of
On Sat, 21 Oct 2000 10:46:13 EDT, the world broke into rejoicing as
Eugene Tyurin <[EMAIL PROTECTED]> said:
> Please do *not* go the RDBMS way!
>
> RDBMS are sexy, "industrial-strength" and stuff. But unless you need to
> ensure consistency of multiple reads/writes on the same table they only
>
