Thanks for the clear explanation. I've just added this case to CAY-201 as
At 02:18 15-10-2004, you wrote:
>On Oct 14, 2004, at 3:44 PM, Mike Kienenberger wrote:
>>Bleah, I meant CAY-201, not 79. Of course 79 does the inverse of what you
>>asked for for OpenBase, so it's still a good example :)
>Adding to what Mike said, I want to point out again that when you map an
>attribute in the Modeler, you select a JDBC type from the dropdown. JDBC
>types are generic and DB-independent. They are mapped to each DB set of
>types via adapter types.xml. types.xml is only used during the table
>schema generation *in the Modeler*. Runtime is not affected, so for
>example you can manually modify schema script replacing TIMESTAMP with
>DATETIME, and keep using JDBC TIMESTAMP in the mapping.
>Also I would appreciate if you post this MySQL-specific case as a comment
>for CAY-201. I am already thinking we should provide an extra column in
>the modeler to optionally allow DB-specific types to be selected manually.
>This should help for cases like this one and generally add more flexibility.
This archive was generated by hypermail 2.0.0 : Fri Oct 15 2004 - 03:51:07 EDT