I think, mangling of tablenames does only make sense in the case of
forward engineering when the orm metadata and the SQL schema are generated.
Well, we could just throw a StupidUserException, or we could take remedial
action. Not part of the JDO spec so we can do as we please, and we have
Hi Andy,
I mixed up the max length of SQL92 identifiers: 128 is correct.
Regards,
Michael
I think, mangling of tablenames does only make sense in the case of
forward engineering when the orm metadata and the SQL schema are generated.
Well, we could just throw a StupidUserException, or we
Hi Michelle,
the next 5 mails you'll receive in the next minutes will contain one
patch file each. These patch files contains changes for assertions A7,
A8. The changes to the last patches of these assertions are:
- Bug fix concerning the class hierarchy of pc classes in package
Quoting Andy Jefferson [EMAIL PROTECTED]:
Where the 30 chars table name length in JPOX came from ? you need to ask Erik
since he added support for Cloudscape 10+ (aka Derby). I know that I *can*
create a table with name of length 30, so removing the restriction of 30
seems possible, but maybe
Hi Michelle,Michael and I were talking this morning about a related issue with reading an object model and making some of the instances persistent. The test case we were talking about was the CompletenessTest but the results were relevant.What we decided as an approach is to define another object
Hi Michelle,The addrid field is a persistent field in the application domain, and should be mapped in both application and datastore identity cases. I think the easiest way to do it is to add field mapping and column ADDRID to the schema and mapping files. Even though addrid is not the identity
The jdoDetachedState is an Object[ ] that consists of:
...
BitSet modifiedFields
Who is keeping this bitset updated when a field changes?
