Well, the upgrade step is a byproduct of this being a bug to begin with. We shouldn't be ignoring schemas if they're specified . . . If people are relying on that behavior though, there's not much we can do with regards to fixing the bug. -- Kevin
On Sat, Aug 16, 2008 at 4:20 PM, Andrus Adamchik <[EMAIL PROTECTED]>wrote: > I have doubts about this approach, aside from the fact that we will force > an upgrade step on everyone using schemas. How is this going to work with > sequence-based pk generators? > > Maybe the PK generation supporting objects themselves should be prefixed > with schema names (as an option I guess) instead of storing the schema in > the lookup table? > > Thoughts? > > Andrus > > > > On Aug 16, 2008, at 10:58 PM, Kevin Menard wrote: > >> In order to fix CAY-539 and CAY-730, I'm changing the default >> JdbcPkGenerator use fullyQualifiedNames. For anyone not using a schema, >> this shouldn't be a problem. For those using schemas, but relying on >> Cayenne to ignore them, they're going to have to delete the schema in >> order >> for things to work. >> In theory this all should be fine . . . getFullyQualifiedName() falls back >> to getName() if appropriate. However, this is used by a fair number of >> the >> DbAdapters and I want to make sure that I haven't broken anything. Thus, >> testing on as many DBs as possible would be nice. I'd appreciate any help >> in this regard, whether it come from Hudson or other team members. >> Otherwise, I'll be a bit reluctant to make the change, just because I >> don't >> want to break anything on anyone. I'll obviously test on whatever >> platforms >> I can. >> >> -- >> Kevin >> > >
