Update RDBMSProcessor to have configuration-driven database translator

Question

Update RDBMSProcessor to have configuration-driven database translator

Opened this issue 10 years ago · 4 comments

derek63 commented 10 years ago

Right now it is hard-coded to ORACLE (which is fine because that is the only one we have so far).

Line 87: List inputStmt = Translator.ORACLE.translate(rdbmsContext);

We should make this configuration driven so the correct translator is selected at run-time.

Answer 1 · 2014-09-15T20:15:58.000Z

Can get this from the datastore configuration, right?

Answer 2 · 2014-09-22T12:43:47.000Z

For me no problem to change it, but I think it is a bit pointless as there isnt any other implementation right now, but if you guys want I can change it

Answer 3 · 2014-09-22T13:49:29.000Z

I can see something like MySQL/MariaDB coming along quickly (we have teams using them internally). We could leave this issue to be solved until then, but I feel it may be best to get it as a nice-to-have soon since it'll be clear what is supported by the configuration.

Answer 4 · 2014-12-16T15:46:03.000Z

Moving this back into ready since it is not done.