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
