It's an unimplemented placeholder for a future version, in which I hope
to implement a basic optimistic concurrency pattern. If your tables have
an integer column dedicated to versioning, Simper will automatically
increment it on every update, after first testing to be sure that the
value hasn't changed. When I implement this, you can choose not to use
it by passing "null" as the column name for the version, which makes
your code today forward-compatible.
The use-case this all supports, is in putting a SimperBean away
somewhere (e.g. in a session variable), pulling it out later (e.g.
during some future HTTP request), and updating the row, without holding
a connection or a transaction the entire time.
Bryan
On Tue, 2002-03-05 at 20:19, John Menke wrote:
The registerTable method takes a String versionColumn as a parameter:
public void registerTable(String tableName, String idColumn, String
versionColumn, IPKGen primaryKeyGenerator)
What is versionColumn used for? In the sample application both of the
example tables set it null. I cannot determine it's purpose.
-john
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
