core-jgi

History

Carlos Ruiz bba1082d4e IDEMPIERE-385 Resolve M_Storage locking and data consistency / Finish changes to database: - view replacement for M_Storage – ad_table marked as view - migration script from M_Storage to the two new tables - migration script to fill M_Warehouse.ReserveLocator_ID - generate UUID columns and model classes for the two new tables - the unique index key m_storagereservation_pkey must have IsSOTrx - reorg unique index key m_storagereonhand_pkey - most accessed columns first - m_product_stock_v - restored to previous version based on M_Storage now view - m_product_substituterelated_v - restored to previous version based on M_Storage now view		2012-11-19 16:17:40 -05:00
..
data	FR: [ 2392587 ] Serbian on external dialogs	2008-12-05 14:53:57 +00:00
model	IDEMPIERE-215 Costing: Drop M_Product_Costing.	2012-04-04 18:33:37 +08:00
oracle	IDEMPIERE-385 Resolve M_Storage locking and data consistency / Finish changes to database:	2012-11-19 16:17:40 -05:00
postgresql	IDEMPIERE-385 Resolve M_Storage locking and data consistency / Finish changes to database:	2012-11-19 16:17:40 -05:00
sequences	* Feature Request [ 1614535 ]	2006-12-17 15:41:06 +00:00
readme.txt	* split data and model by table	2006-12-28 09:57:50 +00:00

readme.txt

XML File
* model/*.xml
- Adempiere database schema
* data/*.xml
- Adempiere seed data

Datatype difference between Oracle and PostgreSQL
* ID Field map to Integer in postgreSQL and Number(10) in Oracle.
* Integer field map to Integer in postgreSQL, Number(10) in Oracle
  ( 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.
* Timestamp field map to Timestamp in PostgreSQL, DATE in Oracle.
* String field map to varchar in PostgreSQL, nvarchar2 in Oracle

Issue
* 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.

Note
* Integer instead of BigInt will be use as datatype for ID field to maintain compatibility
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.