More than happy to join forces on this as I think it would be valuable to the wider community. While I took a look at the newer SQL parser (which is a very nice addition - the EBNF grammar would be helpful so we can get IntelliJ plugin support for the SQL language), I don't believe the new parser is going to fix the bigger issues that we hit. We had to make a series of changes to Flyway to get where we got to. We're not at all sure that the owner of Flyway would accept the changes given how much we had to change the interface to accommodate the workarounds for a non SQL/JDBC compliant DB (as things stand now).
Our alternate OrientDB API based approach is in development and we're basing it on the same functionality as Flyway (just without Java migration support right now since we've not used that functionality in Flyway in over a year) On Mon, Feb 16, 2015 at 12:06 PM, Fabrizio Fortino < [email protected]> wrote: > Hi Nick, > > I have started to add the OrientDB support for Flyway too and I stumbled > in the same problems you report. AFAIK most of the problems will be sorted > out with the introduction of the new SQL parser / engine (a first version > of the engine has just been pushed in the develop branch!). I will wait for > the new engine to see if I can manage to create a regular Flyway support > through OrientDB JDBC. Perhaps we can work together on this? I can push the > changes on my Flyway fork in the next days. > > > On Monday, February 16, 2015 at 4:43:53 PM UTC, Nick Pratt wrote: >> >> Thanks, but Im looking to how we would execute this via a SQL command - i >> merely presented the console as the simplest example :-) >> >> I tried to execute this via the Java API, but got the same error message. >> >> We're ultimately trying to make a Flyway/Liquibase CI platform for >> OrientDB. We started by modifying Flyway to add support for OrientDB, but >> the OrientDB JDBC driver is so far out of spec we gave up on that approach >> (no returned generated keys, no default keyword support, parameterized >> statements aren't supported, OrientDB uses [] rather than () for IN >> clauses, Orient doesn't handle quoted class names/fields the same way most >> other RDBMS's do, lack of auto-increment/sequence support, some weird >> issues with white-space (or lack thereof) ) and decided to do a separate >> project just for OrientDB and use the Orient Java Document API directly. >> >> On Mon, Feb 16, 2015 at 11:11 AM, Fabrizio Fortino <[email protected] >> > wrote: >> >>> Hi Nick, >>> >>> From console you can execute the command >>> >>> > *classes* >>> >>> If you need to get information about a specific class, execute: >>> >>> > *info class MyClassName* >>> >>> Execute *help t*o see the list of available commands. >>> >>> Hope it helps, >>> Fabrizio >>> >>> >>> On Monday, February 16, 2015 at 3:00:59 PM UTC, Nick Pratt wrote: >>>> >>>> Thanks Luigi - how do we execute this? >>>> >>>> When we tried from the console and in a code-test, we get: >>>> >>>> orientdb {db=GratefulDeadConcerts}> select expand(classes) from >>>> metadata:schema >>>> >>>> Error: com.orientechnologies.orient.core.exception.OStorageException: >>>> Cannot route COMMAND operation to the distributed node >>>> >>>> Error: >>>> com.orientechnologies.orient.server.distributed.ODistributedException: >>>> No nodes configured for partition 'GratefulDeadConcerts.[internal]' >>>> request: id=-1 from=node1 task=command_sql(select expand(classes) from >>>> metadata:schema) userName=admin >>>> >>>> On Mon, Feb 16, 2015 at 3:17 AM, Luigi Dell'Aquila < >>>> [email protected]> wrote: >>>> >>>>> Hi Nick, >>>>> >>>>> I think this is what you need: >>>>> >>>>> select expand(classes) from metadata:schema >>>>> >>>>> >>>>> 2015-02-13 18:48 GMT+01:00 Nick Pratt <[email protected]>: >>>>> >>>>>> Does OrientDB have a concept of a system catalog that we can query to >>>>>> inspect DB metadata? >>>>>> >>>>>> -- >>>>>> >>>>>> --- >>>>>> 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]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>>>> >>>>> --- >>>>> 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]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> >>> --- >>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > > --- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- --- 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]. For more options, visit https://groups.google.com/d/optout.
