Maybe for now to minimize compatibility issues we merely fix the table name for the one introduced in CAS 3.3 and leave the others as is. Going forward we should be more careful about testing on other databases besides HSQL and MySQL.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Wed, Oct 15, 2008 at 1:51 PM, Marvin S. Addison <[EMAIL PROTECTED]> wrote: > Created http://www.ja-sig.org/issues/browse/CAS-707 and attached a > simple patch that provides Oracle-compatible identifiers. This is a > quick-and-dirty fix, but it's a fix. Downside is it breaks backward > compatibility. Upside is it creates a much more RDBMS-like schema. I > opted for lower-case identifiers, but you might change to upper case > for conformity with TicketGrantingTicketImpl and ServiceTicketImpl. > > As noted on the issue, I think a better solution is to figure out the > build issues that prevent use of an XML mapping file and go that route > if possible. > > M > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
