Re: [Openbravo-development] Change in export.database

2009-10-06 Thread Rafa Roda @ Openbravo
Thanks Antonio, The distribution is now clear. But why, for example, both MasterData.xml [1] and AD_LANGUAGE.xml [2] have the list of languages? For fixing issue "0010793: It is needed to ad es_CU to AD_Language" [3], do we need to: - Modify only AD_LANGUAGE? - Modify only MasterData.xml?

Re: [Openbravo-development] Change in export.database

2009-10-06 Thread Antonio Moreno
Hi Rafa, A short explanation: sourcedata: this is our application dictionary information. Things like ad_tables, ad_columns, ad_windows go here. This can be extended through modules (modules can add information here), and is updated on each Core update (through update.database). referencedda

Re: [Openbravo-development] Change in export.database

2009-10-06 Thread Antonio Moreno
Hi Rafa, A short explanation: *sourcedata:* this is our application dictionary information. Things like ad_tables, ad_columns, ad_windows go here. This can be extended through modules (modules can add information here), and is updated on each Core update (through update.database). *referenced

Re: [Openbravo-development] Change in export.database

2009-10-05 Thread Rafa Roda @ Openbravo
Thanks for the info Antonio. And what is the difference between src-db/database/sourcedata/referencedData content and referencedata/standard/Masterdata.xml file content [1]? Thanks. Rafa Roda Palacios [1] https://code.openbravo.com/erp/devel/pi/log/8826ff1f6706/referencedata/standard/Masterdata

[Openbravo-development] Change in export.database

2009-09-15 Thread Antonio Moreno
Hi, There has been a change in export.database. From now on, the dataset ADRD (which contains tables such as AD_USER, AD_CLIENT, or AD_LANGUAGE, which are filled during the initial database creation process but are not updated during Openbravo ERP upgrades) will not be exported by default. If