We are implementing a system that would use external data in DO.Net LINQ queries. The external data may have various sources (excel worksheet, odbc connection, oracle connection, ...) and will be relatively small : approx 1000 items, 10 columns. This should be configurable, so the type will not be registered in Domain

What would be the best way to do that? I think there 2 possibilities:

  • Using Query.Store<t> with a POCO T type. A temporary table is created by DO.Net each the query is executed.
  • Copy the data in a table that would be dynamically created. A POCO class would be added dynamically to Domain. I don't know if it is possible right now.

What would you recommend? Are my ideas doable?

asked Feb 23 '12 at 04:08

olorin's gravatar image


Hi olorin,

Could you please specify how you are going to use the external data in DataObjects.Net queries? I'm asking because there is a nice support for local collections already.

(Feb 23 '12 at 05:06) Dmitri Maximov Dmitri%20Maximov's gravatar image

Hello Dmitri,

Yes I'm aware of the local collection : actually I'm planning to use it (and we are using it elsewhere already). I was just wondering if it would be possible to do the same thing with a table that would be dynamically created and added after Domain build, or if such a feature is planned.

(Feb 24 '12 at 03:43) olorin olorin's gravatar image

Olorin, so the nature of the table is not temporal? Its lifetime is bound neither to a session nor to a transaction so it should live much longer?

(Feb 27 '12 at 05:35) Dmitri Maximov Dmitri%20Maximov's gravatar image

Yes, the table would not be temporary. However it would be added dynamically after Domain.Build(), and could be altered after Domain.Build(). Writing this I realize this does not seem a very good idea. For your information, I implemented a solution using Query.Store : this is working well for our use case.

(Feb 29 '12 at 04:14) olorin olorin's gravatar image

olorin, I agree that this might not be a good idea for the current DataObjects.Net architecture. I think, you should post an answer with your solution and I will check it as accepted, so anyone could take it as a working scenario.

(Feb 29 '12 at 04:26) Dmitri Maximov Dmitri%20Maximov's gravatar image

One Answer:

So as a result of the discussion in comments, it was decided that Query.Store-powered solution is acceptable in the scenario described.

answered Mar 05 '12 at 07:57

Dmitri%20Maximov's gravatar image

Dmitri Maximov

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