There are few syntax and/or logical errors in Oracle installdb scripts.
1. using quotes "abcd_efg" for tables to have small letters for table names
is correct, but not to use quotes for column names
2. duplicating indexed columns in same table is not allowed
3. syntax errors using DEFAULT CURRENT_TIMESTAMP and NOT NULL
(not null must be after default statement)
Centric CRM 4.1 (Stable and Released)
Core Team
PUBLIC PROFILE
File Submissions
PATCH:Oracle SQL scripts for installdb (revision 17020)
You need to be logged in to post messages
PATCH:Oracle SQL scripts for installdb (revision 17020)
11/3/2006 7:47 AM EST
1.
11/9/2006
11:38 AM
EST
Oracle SQL scripts status at revision 17247:
Scripts are updated but not without some errors.
new_website.sql:
1. Sequence name is longer than 30 chars, name should be without (n) in the
middle of the name
CREATE SEQUENCE web_row_colum_ow_column_id_seq;
2. There no comas at the end of the line where CURRENT_TIMESTAMP is used
...TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,
2.
11/10/2006
8:28 AM
EST
Thanks! Fixes applied.
3.
11/10/2006
10:55 AM
EST
There are problems with SQL statements with Oracle database deployment.
Problem is with asterisk (a.*) usages in references (should by avoided).
If we need database independence, must be stricter in column selection (not using asterisk sign, and put aliases for column names to avoid duplication of column names).
This should be working with all listed databases.
Patches are included.
4.
11/13/2006
11:01 PM
EST
Thanks again... these have been applied and tested (under DB2). The SELECT fields are typically the same for base and list classes, so User and UserList, CFSNote and CFSNoteList have been updated and the renamed access_assistant was changed in the buildRecord as well.
In general, how would you say the Oracle install is working?
4 results found