What's the proper way to have tables not maintained by do in a database containing the tables of a domain managed by Do.Net?

Let's say that for some reason I need to dynamically create tables, or I that I have a table used by another (not DO.Net) application I want to access only in SQL... It's the not a real demand : but may happen in the life of our application.

With DO 3.X only tables with proper prefix (do) were changed/remove/... by Do.Net : is there a similar mechanism?


This thread was imported from our support forum. The original discussion may contain more detailed answer.

asked May 04 '10 at 08:10

olorin's gravatar image


One Answer:

DO 4.x doesn't have the appropriate mechanism to filter out tables, not built by DataObjects.Net. The only way I can suggest for now is to locate manually created/maintained tables in a separate database schema and explicitly configure DO.Net connection to operate with another database schema, for example:

<domain name="MyDomain"

answered May 04 '10 at 09:25

Dmitri%20Maximov's gravatar image

Dmitri Maximov

olorin wrote: Well, that's ok with me : this is even cleaner that the old prefix mechanism.

(May 04 '10 at 09:25) Editor Editor's gravatar image


(May 04 '10 at 09:25) Dmitri Maximov Dmitri%20Maximov'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

powered by OSQA