openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dp <lindap...@gmail.com>
Subject Re: CacadeType.Persist problem
Date Sat, 21 May 2011 00:56:31 GMT
a few things for discussion:

1. for BatchingPreparedStatementManagerImpl, should flushSingleRow be
implemented the same way as flushAndUpdate of PreparedStatementManagerImpl?
I mean, autoAssignedColumns should be populated for flushSingleRow.

2. Should foreign key values in RowImpl be stored as" by reference" instead
of "by value"? so that when the foreign tables are updated, foreign key
values will be automatically updated, especially, for CascadeType.Persist.

3. If row.getAction() == Row.ACTION_INSERT &&
row.getTable().getAutoAssignedColumns() != null, should this
PreparedStatement not be processed as batch? otherwise, the
autoAssignedColumns might not be able to be populated during batch process.

Regards,
Dapeng

--
View this message in context: http://openjpa.208410.n2.nabble.com/CacadeType-Persist-problem-tp6367387p6388333.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message