midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* split data and model by table 

* sync with 3.1.3 changes
This commit is contained in:
Heng Sin Low 2006-12-28 09:57:50 +00:00
parent bb98109321
commit 8fe3373996
2 changed files with 8 additions and 21727 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21719
db/ddlutils/adempiere-model.xml
View File

File diff suppressed because it is too large Load Diff

14
db/ddlutils/readme.txt
View File

@ -1,8 +1,8 @@
XML File XML File
* adempiere-model.xml * model/*.xml
- DB independent adempiere schema - Adempiere database schema
* adempiere-data.jar * data/*.xml
- DB independent adempiere seed data - Adempiere seed data
Datatype difference between Oracle and PostgreSQL Datatype difference between Oracle and PostgreSQL
* ID Field map to Integer in postgreSQL and Number(10) in Oracle. * ID Field map to Integer in postgreSQL and Number(10) in Oracle.
@ -10,14 +10,14 @@ Datatype difference between Oracle and PostgreSQL
( Oracle's Integer datatype map to number(38) which is not standard) ( Oracle's Integer datatype map to number(38) which is not standard)
* PostgreSQL have no native support for CLOB and BLOB, BYTEA is use instead. * PostgreSQL have no native support for CLOB and BLOB, BYTEA is use instead.
* Timestamp field map to Timestamp in PostgreSQL, DATE in Oracle. * Timestamp field map to Timestamp in PostgreSQL, DATE in Oracle.
* String field map to varchar in PostgreSQL, nvarchar2 in Oracle
Issue Issue
* Fyracle script need to be tested by someone with access to the developer kit. * Fyracle script need to be tested by someone with access to the developer kit.
* XML model and data file to be separated by table to ease maintenance. * XML model and data file to be separated by table to ease maintenance.
Note Note
* SQL standard varchar datatype is use in place of Oracle's non standard nvarchar
datatype. This changes means you must create your database to use UTF8 as default
character set.
* Integer instead of BigInt will be use as datatype for ID field to maintain compatibility * Integer instead of BigInt will be use as datatype for ID field to maintain compatibility
with existing schema. with existing schema.
* The script for Oracle create plsql functions instead of sqlj functions to support Oracle XE.
* The script is not compatible with the original ddlutils library.