Home » Developer & Programmer » Data Integration » Best Practice When a physical object (table/view) is modified (owb
Best Practice When a physical object (table/view) is modified [message #378353] Tue, 30 December 2008 02:19
Messages: 204
Registered: November 2006
Senior Member
Hi Guys,

I just wanted to inquire on the following.

Lets say i have a table, which is already being used in the mapping. It has 3 columns. Lets call this mapping -> map1

Now new columns are created in this table (additional two), and its being used in another mapping. Lets call this mapping -> map2

And since this new columns is not used in map1, shall i reimport the table so that the repository has the latest structure or shall i just leave map1 as it is.

I have tested that even if i dont sycronize table in map1 with the new table structure, the mapping will still work fine, but appreaciate if you guys can suggest whats the best practice. Thanks alot

[Updated on: Tue, 30 December 2008 02:20]

Report message to a moderator

Previous Topic: import flat files
Next Topic: Tracking where a particular db object is used in owb project/mapping
Goto Forum:

Current Time: Sat Feb 04 03:23:39 CST 2023