Eloquera - object database with SQL

After several attempts to write something connected and short about Eloquera, I decided to publish some questions and answers to them - at the same time

Q1: First of all, what is Eloquera? What does it eat? How does it even look like?

A1: Eloquera is an object-relational database with SQL support. Eat it with .NET, in particular, with C #. Theoretically, one should work with any .NET language, but we checked only with C # and VB.NET.
')
And it looks like this:

//
DB db = new DB("server=localhost;user=sys;password=pwd;options=none;");

//
Book book = new Book() { Price = 12.99, Title = "Learn CSV in 365 days" };

//
db.Insert(new Book());

//
var books = db.ExecuteQuery("SELECT Book WHERE Price < 15 AND Title CONTAINS 'learn'");

//
foreach(Book ibook in books)
Console.WriteLine("{0} - ${1}", ibook.Title, ibook.Price);



Q2: What is special about it? Why, for example, not db4o?

A2: Compared with existing object bases, Eloquera is fast, even very, especially when comparing bases to millions of objects and tens and hundreds of types. But this is not enough. It contains such things as regular expressions in SQL, as well as the ALMOST statement . And compared to db4o, Eloquera has no limitations in the size of the database, can index fields and class properties, supports SQL, and it is faster.

Q3: Can I download Eloquera and try?

A3: We are currently working on Eloquera, and have released Eloquera Lite , a client / server version with support for simple objects and no transactions. Despite the lack of transactions in Eloquera Lite, the server supports multiple users and allows you to simultaneously perform multiple requests.

Q4: Is it true that Eloquera uses SQL for queries?

A4: Yes, it happened. The developers of Eloquera, including myself, turned out to be conservative people, and did not understand the beauty of object-oriented ways to request data in short pieces of code of 30 lines each. Therefore, we decided that SQL is very convenient and practical, although not too conceptually for an object base. Well, it means that we have turned out not a concept, but a practical product. You can also try SQL for Eloquera, you can learn by practicing online !

Q5: How long to study working with Eloquera?

A5: Depending on the speed of your reading - from 20 seconds to a minute .

Q6: By the way, do you have JOINs in the database?

A6: Eloquera Lite does not yet support various objects in one request. But we are working on a full version that will support nested objects. And you, colleagues, we would like to ask: what is better - nested objects or JOINs? Write your opinion in the comments and we will discuss all your suggestions.