Issue Details (XML | Word | Printable)

Key: EQX-146
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Matt Raible
Reporter: Marc Logemann
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
AppFuse Light

make incrementer definition dynamic depending on DB selection

Created: 15/May/07 05:24 PM   Updated: 27/Nov/07 03:36 PM   Resolved: 27/Nov/07 03:36 PM
Component/s: DAO Layer
Affects Version/s: 1.8-beta
Fix Version/s: 1.8.1

Environment: 1.8 beta in wicket/iBatis mode


 Description  « Hide
applicationContext-iBatis.xml should use a PropertyPlaceholderConfigurer or something to reflect the used DB as defined in jdbc.properties. If its MySQL, use a MySQLMaxValueIncrementer bean instead of a postgres one.

A very first poor attempt would be to supply a another context which you can use instead of the original one like applicationContext-ibatis.xml.mysql by simply copying to the original name.

Marc Logemann added a comment - 15/May/07 05:26 PM
just saw EQX-63, of course its related to that problem in the first place.

Matt Raible made changes - 15/May/07 09:50 PM
Field Original Value New Value
Fix Version/s 1.8 [ 10100 ]
Matt Raible made changes - 07/Sep/07 11:39 AM
Comment [ It's be a lot easier if iBATIS supported getGeneratedKeys():

http://issues.apache.org/jira/browse/IBATIS-142

If PropertyPlaceholderConfigurer is capable of replacing the "class" attribute on a bean, I could try using that. ]
Matt Raible added a comment - 07/Sep/07 11:39 AM
It'd be a lot easier if iBATIS supported getGeneratedKeys():

http://issues.apache.org/jira/browse/IBATIS-142

If PropertyPlaceholderConfigurer is capable of replacing the "class" attribute on a bean, I could try using that.

Matt Raible made changes - 07/Sep/07 11:47 AM
Fix Version/s 1.8.1 [ 10170 ]
Fix Version/s 1.8 [ 10100 ]
Matt Raible made changes - 27/Nov/07 03:36 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]