Yes, a code example from an online tutorial:
<entity class="org.datanucleus.samples.jpa.tutorial.Book"
name="Book">
<table name="JPA_BOOKS"/>
<attributes>
<basic name="isbn">
<column name="ISBN" length="20"></column>
</basic>
</attributes>
</entity>
But we're more than willing to change the default mapping (using the
mapping file or annotations, both are equivalent) if it seems we are
using names (like size or comment) that may not be accepted by default
by some databases. I'd just like someone to do the necessary changes,
test the result and provide a simple patch, as I don't have a Oracle db
I can test any changes on ...
Kris
Quoting SBalakrishnan <Sanjay.Balakrishnan(a)fnis.com>:
Thanks for the responses.
Is there a way we could achieve the same (Java class annotations),
with changes to the JPA mapping file only(orm.xml),without code
changes.
Thanks
Sanjay
Kris Verlaenen wrote:
>
> Sanjay,
>
> Didn't know Oracle still defines so much restrictions. Could you
test
> which changes are required to make the mapping work in Oracle as
well?
> You can easily change table and column names by adding the
appropriate
> annotations in the corresponding Java classes:
> @Table(name = "xxx") for annotating the class
> @Column(name = "xxx") for annotating the getter
>
> If you would send me these changes, I will gladly check whether we
could
> include them in the build so that it is possible to use Orable by
> default as well.
>
> Kris
>
> Quoting SBalakrishnan <Sanjay.Balakrishnan(a)fnis.com>:
>
>>
>> Hi,
>>
>> Pasted below are the problems, the whole list is in the attached
>> file
>> DroolsTableCreationErrorLog..txt (with my intial post).
>>
>> Thanks again.
>>
>> -Sanjay
>>
>> SEVERE: Unsuccessful: create table Attachment (id number(19,0)
not
>> null,
>> accessType number(10,0), attachedAt timestamp,
attachmentContentId
>> number(19,0) not null, contentType varchar2(255 char), name
>> varchar2(255
>> char), size number(10,0) not null, attachedBy_id varchar2(255
char),
>> TaskData_Attachments_Id number(19,0), primary key (id))
>> Aug 25, 2009 3:21:40 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00904: : invalid identifier
>>
>> Aug 25, 2009 3:21:40 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table Comment (id number(19,0) not
>> null,
>> addedAt timestamp, text clob, addedBy_id varchar2(255 char),
>> TaskData_Comments_Id number(19,0), primary key (id))
>> Aug 25, 2009 3:21:40 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00903: invalid table name
>>
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table Deadline (id number(19,0) not
>> null, date
>> timestamp, escalated number(1,0) not null,
>> Deadlines_StartDeadLine_Id
>> number(19,0), Deadlines_EndDeadLine_Id number(19,0), primary key
>> (id))
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00904: : invalid identifier
>>
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
>> Notification_BusinessAdministrators
>> (task_id number(19,0) not null, entity_id varchar2(255 char) not
>> null)
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
>> Notification_EmailNotificationHeader
>> (Notification_id number(19,0) not null, emailHeaders_id
number(19,0)
>> not
>> null, mapkey varchar2(255 char), primary key (Notification_id,
>> mapkey),
>> unique (emailHeaders_id))
>> Aug 25, 2009 3:21:41 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>> Aug 25, 2009 3:21:42 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
>> PeopleAssignments_BusinessAdministrators
>> (task_id number(19,0) not null, entity_id varchar2(255 char) not
>> null)
>> Aug 25, 2009 3:21:42 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>> Aug 25, 2009 3:21:42 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
PeopleAssignments_ExcludedOwners
>> (task_id
>> number(19,0) not null, entity_id varchar2(255 char) not null)
>> Aug 25, 2009 3:21:42 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>> Aug 25, 2009 3:21:43 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
PeopleAssignments_PotentialOwners
>> (task_id number(19,0) not null, entity_id varchar2(255 char) not
>> null)
>> Aug 25, 2009 3:21:43 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>> Aug 25, 2009 3:21:43 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: Unsuccessful: create table
>> PeopleAssignments_TaskStakeholders
>> (task_id number(19,0) not null, entity_id varchar2(255 char) not
>> null)
>> Aug 25, 2009 3:21:43 PM org.hibernate.tool.hbm2ddl.SchemaExport
>> create
>> SEVERE: ORA-00972: identifier is too long
>>
>>
>>
>>
>> Mauricio Salatino wrote:
>> >
>> > Yes, I run it with postgreSQL and MySQL without problems..
>> > Can you post the problems here?
>> >
>> > On Tue, Aug 25, 2009 at 4:29 PM, SBalakrishnan
>> > <Sanjay.Balakrishnan(a)fnis.com
>> >> wrote:
>> >
>> >>
>> >> Hi,
>> >>
>> >> Eventually we plan to use oracle for persistence,
>> >> hence I pointed my persistence.xml (Human Task component) to
an
>> Oracle
>> >> Database 10g instance
>> >> and immediately ran into
>> >> a number of critical issues (invalid identifiers,reserved names
,
>> and
>> >> identifier is too long etc.).
>> >>
>> >>
>> >> The logs are attached. Am I missing something ? Have others
used
>> other
>> >> databases apart from the default (H2) ?
>> >>
>> >>
>> >> Thanks in advance
>> >>
>> >> Sanjay
>> >>
>>
http://www.nabble.com/file/p25144010/DroolsTableCreationErrorLog..txt
>> >> DroolsTableCreationErrorLog..txt
>> >> --
>> >> View this message in context:
>> >>
>>
>
>> >> Sent from the drools - user mailing list archive
at
Nabble.com.
>> >>
>> >> _______________________________________________
>> >> rules-users mailing list
>> >> rules-users(a)lists.jboss.org
>> >>
https://lists.jboss.org/mailman/listinfo/rules-users
>> >>
>> >
>> >
>> >
>> > --
>> > -
http://salaboy.wordpress.com
>> > -
http://www.jbug.com.ar
>> > - Salatino "Salaboy" Mauricio -
>> >
>> > _______________________________________________
>> > rules-users mailing list
>> > rules-users(a)lists.jboss.org
>> >
https://lists.jboss.org/mailman/listinfo/rules-users
>> >
>> >
>>
>> --
>> View this message in context:
>>
>
>> Sent from the drools - user mailing list archive at
Nabble.com.
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>
>
>
>
> Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
--
View this message in context:
Sent from the drools - user mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users