Does anyone know why the Oracle dialect doesn't generate table names that match the Oracle specification?
Worst case is we break backwards compatibility and change the table names. Seems more feasible than getting Oracle to fix its stupid limitation.... -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Oct 14, 2008 at 4:44 PM, Marvin S. Addison <[EMAIL PROTECTED]> wrote: > This is a rather serious limitation for us. We rolled our own > JDBC-backed registered services impl based on 3.0.x and have happily > used Oracle for almost 2 years now. We are planning a migration to > 3.3, but need a resolution to this issue before we can move forward. > > We'd be happy to open a Jira issue and supply a patch, but I wanted to > discuss possible solutions at a high level beforehand. > > It seems leveraging the <mapping-file> attribute of persistence.xml > would be the way to go, allowing CAS consumers to override table and > field mappings by editing XML configuration. If you do nothing, you > get what you have currently to address the backwards compatibility > issue. Folks on Oracle would need to supply a mapping file with > identifiers that respected the 30-char Oracle limit. > > Problem with the above approach is the build system. Currently > persistence.xml is in the core module, but it seems you'd want the > mapping file alongside deployerConfigContext.xml in the webapp module > for ease of configuration. The problem then is that there's no good > way to reference a mapping file outside of the jar containing > persistence.xml. Although you could possibly use a jar: classpath to > get at a mapping file in another module in the deployed WAR, I don't > believe all classloaders support it and it's pretty icky besides. It > seems moving persistence.xml into the webapp module isn't right > either. > > Thoughts and suggestions welcome. > > Thanks, > Marvin Addison > Middleware Services > Virginia Tech > > On Sat, Oct 4, 2008 at 12:40 PM, Scott Battaglia > <[EMAIL PROTECTED]> wrote: > > The allowedAttributes table is an additional table that stores which > > attributes are mapped to a service. Unfortunately we're allowing > Hibernate > > to generate the table names instead of explicitly specifying them. I'm > > surprised hibernate won't generate appropriate sized ones though. You > can > > open a JIRA issue for this and we'll take a look though I can't promise I > > know how to fix it other than specifically naming the table which would > > break backwards compatibility. :-/ > > > > -Scott > > > > -Scott Battaglia > > PGP Public Key Id: 0x383733AA > > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > > > > On Tue, Sep 30, 2008 at 3:23 PM, Chuck Pearson <[EMAIL PROTECTED] > > > > wrote: > >> > >> I'm really new to CAS and Service Management but can someone tell me how > >> to use the Oracle10gDialect. I am attempting to add my first service > and I > >> get these errors when attempting to create Oracle database tables. > >> > >> I can create the REGISTEREDSERVICEIMPL, SERVICETICKET, & > >> TICKETGRANTINGTICKET tables just fine, but my table name is too long > for. > >> " > >> 2008-09-30 14:16:27,376 DEBUG [org.hibernate.tool.hbm2ddl.SchemaUpdate] > - > >> <create table RegisteredServiceImpl_allowedAttributes > >> (RegisteredServiceImpl_id number(19,0) not null, element varchar2(255 > char), > >> allowed_attribute_id number(10,0) not null, primary key > >> (RegisteredServiceImpl_id, allowed_attribute_id))> > >> 2008-09-30 14:16:27,391 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] > - > >> <Unsuccessful: create table RegisteredServiceImpl_allowedAttributes > >> (RegisteredServiceImpl_id number(19,0) not null, element varchar2(255 > char), > >> allowed_attribute_id number(10,0) not null, primary key > >> (RegisteredServiceImpl_id, allowed_attribute_id))> > >> 2008-09-30 14:16:27,391 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] > - > >> <ORA-00972: identifier is too long > >> " > >> > >> I was expecting the table name to be just " RegisteredServiceImpl " but > it > >> seems to default to the above longer name which is greater than 30 > >> characters. > >> > >> Thanks for any and all suggestions. > >> Chuck > >> _______________________________________________ > >> 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 > > > > > _______________________________________________ > 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
