Hi, the focus of SQL is not just querying, but also data definition and full database administration. Which is fine, but different to AQL, which currently focuses on data selection and manipulation. This may change in the long run, but that's how it is at the moment.
The main issue that prevents us from adding this feature at the moment is that creating a new collection currently cannot be part of a transaction. So rolling back the AQL query (which is a transaction) that created the new collection would cause issues. The query then would become non-transactional. Best regards Jan Am Samstag, 12. November 2016 06:41:56 UTC+1 schrieb Andreas Jung: > > Sorry but this is hair splitting :). > > SQL is also a query language and I can do something like > > SELECT .... INTO non_existing_table > > I do not see a problem why this should not be possible in AQL too. Either > implicitly or perhaps using an extra keyword. > > -aj > > Am Montag, 7. November 2016 15:13:09 UTC+1 schrieb Simran Brucherseifer: >> >> In more fancy words (quotes from the docs): >> >> AQL supports reading and modifying collection data, but it doesn't >>> support data-definition operations such as creating and dropping databases, >>> collections and indexes. It is a pure data manipulation language (DML), not >>> a data definition language (DDL) or a data control language (DCL). >> >> >> https://docs.arangodb.com/3.1/AQL/ >> > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
