Thank you. Do you have a tutorial of how to take classic sql db and migrate it to orient? I don't need a technical tutorial, more of a conceptual one, how old sql db will look like in orient db. Thanks
On Tuesday, June 18, 2019 at 1:08:28 PM UTC+3, Gianluigi Belli wrote: > > 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 orient-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/orient-database/0d709c73-f762-4d5c-87c1-f56adb38b4b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
