|
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:
What would you recommend? Are my ideas doable? |
|
So as a result of the discussion in comments, it was decided that |
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.
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.
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?
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.
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.