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).
referenceddata: this is information referenced by sourcedata,
like ad_client, ad_org, ad_user, ad_language, or ad_role. The Openbravo
database cannot be created without this information (the referencial
integrity of the database would be compromised without it), and this
explains why it is treated in a special way. It is not updated on each
Core update.
masterdata: this is information which is not needed to create
the database, but it's really convenient for every user, like contries,
or currencies. This is also not updated on each Core update.
sampledata (smallbazaar, bigbazaar): this is sample information
we provide for the users to test openbravo, and contains a new client,
with its corresponding business information.
Hope it clears the issue a bit. Regards,
Antonio.
Rafa Roda @ Openbravo wrote:
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.xml
2009/9/15 Antonio Moreno <antonio.mor...@openbravo.com>
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 you want to export their data, you need to specify the
-Drd=true option in export.database:
ant export.database -Drd=true
As part of this change, the xml data files related to these tables has
been moved from plan src-db/database/sourcedata to the new folder
src-db/database/sourcedata/referencedData.
This change is only relevant to Openbravo Core developers, not to module
developers, as modules cannot modify the content of these tables by
normal means (ie., they need to create a dataset for it, and this works
as usual).
Regards,
Antonio Moreno.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF,
CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and
stay
ahead of the curve. Join us from November 9-12, 2009. Register
now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
|
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
