For better performance it's best to let the database engine (depends on database vendor) generate a unique id when needed. In high usage systems you will see contention on those sequence tables which will hold back performance.
________________________________ From: jill han [mailto:[EMAIL PROTECTED] Sent: Thu 21/06/2007 22:32 To: Apache Torque Users List Subject: application sequence vs table sequence In the application, just one sequence is created, object_id_seq, to generate the object_id for all the tables in the db. Do you think each table should have its own sequence? Which is better, i.e., one sequence for entire db(schema) or multiple sequences for each table, in terms of performance? Thanks for your helps. Jill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are the intended recipient, you must treat the information in confidence and in accordance with all laws related to the privacy and confidentiality of such information. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies of this email, including all attachments.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
