Hi Alexander, Apologies for the issues being encountered, but we are as always striving to make the Entity Framework support in the Virtuoso ADO.Net Provider better and are already working on fixing the issue reported by Alex Efimov and should have a fix for this soon, which is also related the BIG INT support in the provider he reported previously and is already fixed (support has been added).
In terms of what would be the best approach obviously writing to the entity framework architecturally is the most efficient/modern/recommended approach from the application programmers point of view, but you can always code directly to ADO.Net which is more mature and stable but requires a lot more work on your part probably and understandably you would like to avoid, but it is an option. In terms of stabilising the Entity Framework layer we are absolutely committed to doing this, which is proving quite challenging due to the extremely complex queries generated by the EDM (which was only really designed to work with SQLServer I might add) and hence any changes to made on the server side have to be doubly and triply checked we are finding to ensure they do not have adverse affects on the Entity Framework layer. Thus we are also seeking to extend to the test module for this provider to ensure we have test coverage for all possible EDM query types/scenarios and hence provide a more stable and robust provider going forward. In terms of using Virtuoso as an RDBMS store, if you are to using it as an RDF store then you absolutely should be using it is an RDBMS store this being its origin and what the RDF store is build upon, the issue is simply one of stabilising the Entity Framework component of the ADO.Net Provider. I shall let you know when we have a fix for this issue and the demo application form Alex running to completion ... Best Regards Hugh Williams Professional Services OpenLink Software Web: http://www.openlinksw.com Support: http://support.openlinksw.com Forums: http://boards.openlinksw.com/support Twitter: http://twitter.com/OpenLink On 12 Apr 2010, at 17:08, Alexander Sidorov wrote: > Hello! > > I need to decide can we use Virtuoso as relational storage at production or > not. > > The most significant problem is ADO.NET provider. First we had encoding > problem, then we had EDM generation one. They were fixed, but it took several > months. After that we tried to use it with very simple scenarios and it > didn't work again (my colleague Alex Efimov wrote here about some of these > problems). The most strange thing about these bugs is that they concern the > simplest scenarios I can imagine. > > We use other relational storage now but loose transactional integrity between > the RDBMS and Virtuoso RDF storage. I don't like it but chances we can use > Virtuoso as relational storage are less and less (from bug to bug). And it is > not funny already. > > To take final decision I need answers to two questions: > 1. We tried using ADO.NET provider only with Entity Framework. Is there any > chance ADO.NET provider is more stable for pure ADO.NET. It could be a > temporary measure (ugly and out-of-date measure) to use pure ADO.NET till EF > support is stabilized. > 2. Are there any chances ADO.NET provider will be stabilized in the nearest > future (I mean month or two). > > Regards, > Alexander > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > Virtuoso-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
