Currently when we build a domain we user perform, we want to continue to use to build our schema as much as possible. However, it fails if we add indexes, tables or columns that DO.Net does not know about.

Is there a way to hook into validation to keep it from failing or removing extra indexes, tables, or columns that we want?

For example if we add columns for ETL tie in perform will either remove them or fail. What I would like is to hook into validation so when it runs into an object it does not know about I can bypass the error.

asked Apr 24 '12 at 10:05

MikeBenson's gravatar image


One Answer:

Hello Mike,

unfortunately there is no such API at the moment.

For simplest cases you can add tables to separate schema. They will be invisible for DataObjects.Net.

If there is a simple way to differentiate ETL tables/columns/indexes (like a common name prefix or so), we can implement a work-around for it.

answered Apr 25 '12 at 04:31

Denis%20Krjuchkov's gravatar image

Denis Krjuchkov

Thanks for the offer, but I am not looking for a workaround. I am looking for a solution. EF seems to do it for me.

(Apr 26 '12 at 15:00) MikeBenson MikeBenson's gravatar image
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview


Once you sign in you will be able to subscribe for any updates here



Asked: Apr 24 '12 at 10:05

Seen: 4,005 times

Last updated: Apr 26 '12 at 15:00

powered by OSQA