wisnesky
commented
4 years ago That’s definitely an error, and probably related to CQL<-> Postgres driver interaction. The sql typeside does have a type “Double” (you can write "typeside x = sql” and run it to see everything in the sql typeside), and so my best guess is that CQL is generating SQL code containing the word ‘double’, but Postgres wants to see “double precision” or “double(32)” or something similar. Any chance you can generate a test case, or provide the stack trace (which should be on the console if you run CQL using java -jar cql.jar)? The fix is probably just another ‘if vendor = X write Z instead of Y in the generated SQL’, and there are many corner cases to check. On that note, thank you for being the first person to check them for postgres :-).
On Jul 11, 2020, at 9:44 AM, Tim Pierson notifications@github.com wrote:
is thrown by
command store1 = export_jdbc_instance CoProd "jdbc:postgresql://localhost/foo" ""
Should I be using a different type or should CQL tell the JDBC posgres driver to use "double precision" (instead of "double")?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CategoricalData/CQL/issues/47, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2QKNZY7LIG4NEVP5Q5KPTR3CJHBANCNFSM4OXMDZYQ.
o1lo01ol1o
is thrown by
command store1 = export_jdbc_instance CoProd "jdbc:postgresql://localhost/foo" ""I'm using the following in my typeside:
Should I be using a different type or should CQL tell the JDBC posgres driver to use "double precision" (instead of "double")?