From: Atif S. <ati...@bo...> - 2005-04-29 10:02:32
|
Hi We have a user who's using Oracle 9 on a Windows 2000 server. He has managed to install bodington 2.4.1 but when he setup the tables he gets the following error message: A technical problem occurred trying to setup up tables in the database. java.sql.SQLException: ORA-00972: identifier is too long at Someone (i.e. a developer) has broken the Golden Oracle RULE that names of columns can't be long than 30 characters. The table which has broken this rule is log_book_pages. Could someone fix this problem Quickly? The user is from University of Essex. Thanks :-) ------------------------------------------------------------------------ Subject: RE: Installation of Bodington From: "Scott, John R" <jr...@es...> Date: Fri, 29 Apr 2005 08:39:53 +0100 To: "bodington.org enquiries" <enq...@bo...> > > > Jane, I have now managed to install Bodington and get it to talk to the database. The problem I now have is when using Bodington to set up the database tables. The output message in the browser and Tomcat are in the attached file. I am using Oracle 9 on a Windows 2000 server. Sorry to trouble you again. Is there a direct support email address that I can contact directly? Regards John ------------------------------------------------------------------------ A technical problem occured trying to setup up tables in the database. java.sql.SQLException: ORA-00972: identifier is too long at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at TOMCAT Output EXECUTING SQL STATEMENT ============================================== /* Table contains data fields, a primary key constraNUMERIC(10) and a foreign ke y constraints */ /* The constraints are designed to limit damage to data integrity in the event o f */ /* programmer error or other unforeseen circumstances. */ /* Log book pages are a type of object hence the foreign key reference to object s and */ /* should only occur with reference to specific log books and specific users hen ce foreign */ /* key reference to those tables. */ CREATE TABLE log_book_pages ( log_book_page_id NUMERIC(10) NOT NULL , log_book_id NUMERIC(10) NOT NULL , user_id NUMERIC(10) NOT NULL , flags NUMERIC(10) NOT NULL, when_first DATE NOT NULL , when_last DATE NULL , when_user_first DATE NULL , when_user_last DATE NULL , section_first_big_string_id NUMERIC(10) NULL, section_last_big_string_id NUMERIC(10) NULL, section_user_first_big_string_id NUMERIC(10) NULL, section_user_last_big_string_id NUMERIC(10) NULL, question_first_big_string_id NUMERIC(10) NULL, question_last_big_string_id NUMERIC(10) NULL, question_user_first_big_string_id NUMERIC(10) NULL, question_user_last_big_string_id NUMERIC(10) NULL, acl_id NUMERIC(10) NULL, CONSTRAINT PK_log_book_pages PRIMARY KEY ( log_book_page_id ), CONSTRAINT FK_log_book_pages_to_objects FOREIGN KEY ( log_book_page_id ) REFERENCES objects ( id ), CONSTRAINT FK_pages_to_log_books FOREIGN KEY ( log_book_id ) REFERENCES log_books ( log_book_id ), CONSTRAINT FK_log_book_pages_to_users FOREIGN KEY ( user_id ) REFERENCES users ( user_id ), CONSTRAINT FK_pages_s_f_to_bgstrs FOREIGN KEY ( section_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_l_to_bgstrs FOREIGN KEY ( section_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_u_f_to_bgstrs FOREIGN KEY ( section_user_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_u_l_to_bgstrs FOREIGN KEY ( section_user_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_f_to_bgstrs FOREIGN KEY ( question_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_l_to_bgstrs FOREIGN KEY ( question_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_u_f_to_bgstrs FOREIGN KEY ( question_user_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_u_l_to_bgstrs FOREIGN KEY ( question_user_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_to_acls FOREIGN KEY ( acl_id ) REFERENCES acls ( acl_id ) ) |
From: Adam M. <ada...@co...> - 2005-04-29 15:14:22
|
Dear John Apologies for the delay in responding - all Bodington developers (except Atif) have been in a 2 day meeting until 10 minutes ago. We will fix this bug in the next week. We are going to release version 2.4.3 probably around the end of next week and will include a shorter name in response to your error report. I take it that this bug is from version 2.4.2 of Bodington? Have you found any other problems? If so let us know and assuming that they are easy to fix - then we will include these too. Alexis - I'll put this one down for you. Adam Marshall _____ From: bod...@li... [mailto:bod...@li...] On Behalf Of Atif Suleman Sent: 29 April 2005 11:05 To: bod...@li... Subject: [Bodington-developers] Golden Oracle RULE Hi We have a user who's using Oracle 9 on a Windows 2000 server. He has managed to install bodington 2.4.1 but when he setup the tables he gets the following error message: A technical problem occurred trying to setup up tables in the database. java.sql.SQLException: ORA-00972: identifier is too long at Someone (i.e. a developer) has broken the Golden Oracle RULE that names of columns can't be long than 30 characters. The table which has broken this rule is log_book_pages. Could someone fix this problem Quickly? The user is from University of Essex. Thanks :-) _____ Subject: RE: Installation of Bodington From: "Scott, John R" <mailto:jr...@es...> <jr...@es...> Date: Fri, 29 Apr 2005 08:39:53 +0100 To: "bodington.org enquiries" <mailto:enq...@bo...> <enq...@bo...> Jane, I have now managed to install Bodington and get it to talk to the database. The problem I now have is when using Bodington to set up the database tables. The output message in the browser and Tomcat are in the attached file. I am using Oracle 9 on a Windows 2000 server. Sorry to trouble you again. Is there a direct support email address that I can contact directly? Regards John _____ A technical problem occured trying to setup up tables in the database. java.sql.SQLException: ORA-00972: identifier is too long at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at TOMCAT Output EXECUTING SQL STATEMENT ============================================== /* Table contains data fields, a primary key constraNUMERIC(10) and a foreign ke y constraints */ /* The constraints are designed to limit damage to data integrity in the event o f */ /* programmer error or other unforeseen circumstances. */ /* Log book pages are a type of object hence the foreign key reference to object s and */ /* should only occur with reference to specific log books and specific users hen ce foreign */ /* key reference to those tables. */ CREATE TABLE log_book_pages ( log_book_page_id NUMERIC(10) NOT NULL , log_book_id NUMERIC(10) NOT NULL , user_id NUMERIC(10) NOT NULL , flags NUMERIC(10) NOT NULL, when_first DATE NOT NULL , when_last DATE NULL , when_user_first DATE NULL , when_user_last DATE NULL , section_first_big_string_id NUMERIC(10) NULL, section_last_big_string_id NUMERIC(10) NULL, section_user_first_big_string_id NUMERIC(10) NULL, section_user_last_big_string_id NUMERIC(10) NULL, question_first_big_string_id NUMERIC(10) NULL, question_last_big_string_id NUMERIC(10) NULL, question_user_first_big_string_id NUMERIC(10) NULL, question_user_last_big_string_id NUMERIC(10) NULL, acl_id NUMERIC(10) NULL, CONSTRAINT PK_log_book_pages PRIMARY KEY ( log_book_page_id ), CONSTRAINT FK_log_book_pages_to_objects FOREIGN KEY ( log_book_page_id ) REFERENCES objects ( id ), CONSTRAINT FK_pages_to_log_books FOREIGN KEY ( log_book_id ) REFERENCES log_books ( log_book_id ), CONSTRAINT FK_log_book_pages_to_users FOREIGN KEY ( user_id ) REFERENCES users ( user_id ), CONSTRAINT FK_pages_s_f_to_bgstrs FOREIGN KEY ( section_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_l_to_bgstrs FOREIGN KEY ( section_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_u_f_to_bgstrs FOREIGN KEY ( section_user_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_s_u_l_to_bgstrs FOREIGN KEY ( section_user_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_f_to_bgstrs FOREIGN KEY ( question_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_l_to_bgstrs FOREIGN KEY ( question_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_u_f_to_bgstrs FOREIGN KEY ( question_user_first_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_q_u_l_to_bgstrs FOREIGN KEY ( question_user_last_big_string_id ) REFERENCES big_strings ( big_string_id ), CONSTRAINT FK_pages_to_acls FOREIGN KEY ( acl_id ) REFERENCES acls ( acl_id ) ) |
From: Atif S. <ati...@bo...> - 2005-04-29 15:57:10
|
Adam Marshall wrote: > Apologies for the delay in responding - all Bodington developers > (except Atif) have been in a 2 day meeting until 10 minutes ago. > Let's get the facts straight Adam, there has been no delay in responding to the user John. While you were in the meeting this Morning I responded to the user instantly. Stated the fact we'll have it fixed in the next release and thanked him for reporting this bug. Thanks. |
From: Matthew B. <mat...@co...> - 2005-04-29 17:39:48
|
Adam Marshall wrote: > We will fix this bug in the next week. We are going to release version > 2.4.3 probably around the end of next week and will include a shorter > name in response to your error report. I take it that this bug is from > version 2.4.2 of Bodington? 2.4.1 was the version he was using. This bug came in from version 1.3 of LogBookPage.sql (commited 12/08/2004). As the mapping between database columns and JavaBean properties is stored in the database we don't need to update current installations to fix this problem (unless there is hard coded SQL in LogBookFacility). All new installs should just have these trucated (remove the _id?). Leaving current installs along will probably come back to bite us if we don't alter the column names but it isn't essential for the bug fix. bodington=# select field, length(field) from fields where length(field )> 30; field | length -----------------------------------+-------- section_user_first_big_string_id | 32 section_user_last_big_string_id | 31 question_user_first_big_string_id | 33 question_user_last_big_string_id | 32 -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |
From: Matthew B. <mat...@co...> - 2005-04-29 15:21:56
|
Atif Suleman wrote: > A technical problem occurred trying to setup up tables in the database. > java.sql.SQLException: ORA-00972: identifier is too long at Early versions of PostgreSQL have the same problem with column names over 30 characters. This should probably go into the bug tracker. -- +--Matthew Buckett-----------------------------------------+ | VLE Developer, Learning Technologies Group | | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/ | +------------Computing Services, University of Oxford------+ |