Don Mitchell

06/29/2020, 2:03 PM
I'm writing a Snowflake dialect for exposed. The good news is that 11/19 tests pass 🙂 If you're interested in this work, my fork and branch I'd welcome critiques and help. Right now, it's failing on the prepared statements where somehow the values are not properly going to the payload.
Copy code > javaTimeFunctions STANDARD_OUT
    20:41:39,049  WARN Test worker Exposed:invoke:183 - Transaction attempt #0 failed: java.sql.SQLFeatureNotSupportedException. Statement(s): INSERT INTO CITIESTIME (LOCAL_TIME, "NAME") VALUES (?, ?) java.sql.SQLFeatureNotSupportedException
... > javaTimeFunctions FAILED java.sql.SQLFeatureNotSupportedException
    SQL: [Failed on expanding args for INSERT:]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by (file:/Users/dmitchell/.gradle/caches/modules-2/files-2.1/net.snowflake/snowflake-jdbc/3.12.7/e47fa73b85037285b887c63602f9c509df27b2be/snowflake-jdbc-3.12.7.jar) to constructor java.nio.DirectByteBuffer(long,int)
WARNING: Please consider reporting this to the maintainers of
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
btw: re convo in • I'll check w snowflake re getting a db accessible for exposed testing. I can see a lot of reasons they'd be reluctant (abuse potentials, but) • thanks for the pointer to the methods for indexes. I hadn't found them yet. • the byte issue ends up being a bug in jdbc.snowflake which I've patched but I've also written a guard in exposed to avoid • thanks for the current timestamp pointer, I'd fixed that but there seems several alt code paths which don't pick it up. I think I've got them.
Can the authorities for exposed sign up for a trial snowflake account so that the unit tests will work for others (I'm testing against my company's non-public account)
👀 1