Maybe you should reconsider how badly you want the app to be totally databaseMaybe I can further abstract out the generate unique-id portion, Since unique-id generation does seem to be a pretty common database extension (for some reason...), and then provide a generic schema definition, and a postgresql specific one (along with whatever others I can drum up). The generic one will rely on the software to come up with the unique id in the fashion I'm currently doing.
agnostic? Using a sequence might be less of a contortion than using vacuum
a few times a minute. You are likely to have similar performance issues
with other databases, so this section of code may not turn out to be very
portable in any case.
Speaking of which, is there a better way than what i'm currently doing (when the database doesn't have any such support)? I've heard of one method based on something like "select max(id)+1 from table" but this seems error prone, at the very least, you'd have to have a unique index, and be prepared to redo on failure, which could get messy if its a big transaction, and frequent if there is a lot of concurrent inserting going on.
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
