-
Notifications
You must be signed in to change notification settings - Fork 3
[OEP 4] OrientDB SQL v3 #4
Comments
We have to consider that these changes will impact 3rd party drivers, especially those who have query builders. |
Has there ever been discussion about what SQL commands, not currently supported, could be added in future versions? One of the reasons I started to look at OrientDB was the SQL compatibility. For many of us with years and years of RDBMs having that available highly reduces our onboarding to the product. I am new and still going over the docs, but I think others who have used it longer may have suggestions to that regard. As for considering impact on third party drivers, we could have a period where we have features listed as to be removed in future versions (if removing), however changes to existing commands are much harder since it could potentiall break third party drivers so that needs to be informed to developers Although developers of drivers may be able to do some workaround based on the version of the DB. |
There are many enhancement requests about this in the main issue tracker, I think we should check them and link them here... |
In the UPDATE I think there is a typo:
in ordert to be coherent should be
However, removing REMOVE and UPDATE would break existent queries. Why don't keep it? |
ops, typo... Just fixed it, thanks! From current docs, all the following are supported syntaxes
IMHO the first case is quite clear, the second one is almost acceptable, the third one is just a mess.
But again, we can decide to keep it, the UPDATE REMOVE is not my biggest concern. (but please, let's drop UPDATE PUT, that's really ugly...) Luigi |
sorry, rephrasing
|
we could even do this:
that would be a middle way, but not strong opinion on that actually at the end i would prefer another proposal from luigi:
|
New user here... I would have never expected the update command to allow to drop a field. In Staying close to the SQL standard, when possible, makes it much easier for On Wed, Jun 22, 2016 at 10:59 AM, tglman notifications@github.com wrote:
|
@francisco1844 orientdb is a schemaless/schemamixed database, the |
Implemented, closing |
Summary:
Rationalize current SQL syntax to allow easy, complete and consistent manipulation of multi-model data structures
Goals:
Non-Goals:
Motivation:
OrientDB SQL query syntax/engine is probably the first component that was developed in OrientDB.
In the years, the syntax evolved by addition of new keywords and features, sometimes in a way that is not completely consistent.
The result is that current OrientDB SQL is sometimes ambiguous or incomplete (see orientechnologies/orientdb#5950).
Description:
Redefine the SQL syntax and semantics, validate its consistency.
Some work is already in progress on a parallel docs branch
https://github.com/orientechnologies/orientdb-docs/blob/newexecutor/SQL-Syntax.md https://github.com/orientechnologies/orientdb-docs/blob/newexecutor/SQL-Projections.md https://github.com/orientechnologies/orientdb-docs/blob/newexecutor/SQL-Update.md
Alternatives:
Risks and assumptions:
Impact matrix
The text was updated successfully, but these errors were encountered: