Why? You can associate an index to the property name. You can also create lucene indexes for more complex and fast text-based searches. You can certainly use it for CRM with no concern. Nevertheless, as it's required for any system, you have to work on the architecture of your db in advance. So it's essential to start to think of graphs, vertexes, arcs and classes, instead of tables, tuples and joins. This is the most significant effort. You don't make cartesian products; you traverse paths on nodes and nested documents. Having the SQL can make it easier to start writing queries, but it is of no help in the process to change perspective.
On Monday, June 17, 2019 at 4:05:11 PM UTC+2, GraphPerson wrote: > > Hi, > Can Orien DB be used for style type of apps such as CRM? > Does anybody use it for that kind of a task? > I believe there are disadvantages using it like that. it was probably > designed for relation first query and if you ask information like "select > from customers where name like 'blabla'" you probably pay a price in > performence. > Thanks > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/orient-database/608b6586-9ed8-4bce-8552-b3f0d350fc01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
