Hi Dirk,
transactions...
Another problem might be that if you use a database table, you might
face the problem of coordinating concurrent accesses. For one dbms you might use transactions, for another you might have to do a explicit
'lock table' command. What does your implementation do here?
use a *serializable* transaction for every n inserts (10, 100, 1000 and so on).
It uses the table to keep the high value of the id, while the low value is calculated on the fly in ram (lowValue++) .
If the system crashes and reboots, the first id value retrieved will have an incremented high value.
Example:
0
1
2
3
crash...
10
11
12
13
crash...
20
21
22
etc
Anyway, if we use a plugin system, a developer can provide a specific implementation for a target database.
RegardsDirk
Luca ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
