<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.infinite-erp.co.id/index.php?action=history&amp;feed=atom&amp;title=How_to_exclude_Database_Physical_Objects_From_Model</id>
	<title>How to exclude Database Physical Objects From Model - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.infinite-erp.co.id/index.php?action=history&amp;feed=atom&amp;title=How_to_exclude_Database_Physical_Objects_From_Model"/>
	<link rel="alternate" type="text/html" href="https://wiki.infinite-erp.co.id/index.php?title=How_to_exclude_Database_Physical_Objects_From_Model&amp;action=history"/>
	<updated>2026-04-06T16:45:07Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.31.1</generator>
	<entry>
		<id>https://wiki.infinite-erp.co.id/index.php?title=How_to_exclude_Database_Physical_Objects_From_Model&amp;diff=58&amp;oldid=prev</id>
		<title>Wikiadmin: Created page with &quot;==Objective== Openbravo keeps track of the database physical objects (such as tables, views, functions or triggers) through an utility called [DBSourceManager]. This utility i...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.infinite-erp.co.id/index.php?title=How_to_exclude_Database_Physical_Objects_From_Model&amp;diff=58&amp;oldid=prev"/>
		<updated>2018-10-14T13:50:17Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;==Objective== Openbravo keeps track of the database physical objects (such as tables, views, functions or triggers) through an utility called [DBSourceManager]. This utility i...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;==Objective==&lt;br /&gt;
Openbravo keeps track of the database physical objects (such as tables, views, functions or triggers) through an utility called [DBSourceManager]. This utility is able to export all the database model object definitions to XML files, which are stored in the src-db/database/model folder (both in Core and in modules).&lt;br /&gt;
&lt;br /&gt;
This tool is designed to work in a multiplatform environment, both supporting Oracle and PostgreSQL. This means that sometimes if specific syntax or features of a particular Database Management System are used, the tool might not support them.&lt;br /&gt;
&lt;br /&gt;
In these cases, a possible approach is to create these specific objects using a Module Script (you can find more about them [[How_to_create_build_validations_and_module_scripts|here]]), and then exclude them from the database physical model of Openbravo.&lt;br /&gt;
&lt;br /&gt;
==Excluding objects in modules==&lt;br /&gt;
Objects are excluded through a file called excludeFilter.xml. This file should be located inside the src-db/database/model/ folder of the module (if it doesn't exist, you will need to create it), and it follows a very simple XML format. Here is an example:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
  &amp;lt;vector&amp;gt;&lt;br /&gt;
    &amp;lt;excludedTable name=&amp;quot;TEST_TABLE&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;excludedView name=&amp;quot;TEST_VIEW&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;excludedFunction name=&amp;quot;TEST_FUNCTION&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;excludedTrigger name=&amp;quot;TEST_TRIGGER&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/vector&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This file will exclude the table TEST_TABLE, the view TEST_VIEW, the function TEST_FUNCTION, and the trigger TEST_TRIGGER from the model, and therefore they will be neither exported nor removed,  nor modified in any way during the normal database management tasks (update.database and export.database).&lt;br /&gt;
&lt;br /&gt;
[[Category:HowTo]]&lt;/div&gt;</summary>
		<author><name>Wikiadmin</name></author>
		
	</entry>
</feed>