Since there is no dialect that ships with SQuirreL for this database, you are getting the generic dialect. I looked for info about using telid with hibernate and I saw the following here:
"Many Hibernate use cases assume a data source has the ability (with proper user permissions) to process Data Definition Language (DDL) statements like CREATE TABLE and DROP TABLE as well as Data Manipulation Language (DML) statements like SELECT, UPDATE, INSERT and DELETE. Teiid can handle a broad range of DML, but does not support DDL."
Is it true that all DDL is off the table with this database? If so, that will severely hamper the dialect's support for what SQuirreL can provide (mostly in refactoring). In any case, we can include the dialect and extension to give you at least basic functionality from the SQL scripts plugin.
I'm trying to use the function where I right-click on a table and generate the "Scripts -> Create Table Script". It fails with this error:
org.hibernate.MappingException: No Dialect mapping for JDBC type: 2
I see that date type "2" corresponds to BigDecimal. But I can't figure out if there is anyway for me to specify somewhere what the mapping for this data type should be.
Are the Hibernate dialects hard-coded into .jar files? Is adding this additional mapping outside the scope of a simple configuration change?
In case it matters, I'm using JBoss Enterprise Data Services (the former "Metamatrix" technology which is based on the Teiid project). This is the JDBC driver class:
SQuirreL doesn't really have built-in support for this language. Everything else has worked well for me with the Teiid driver in SQuirreL. I speculate that the Hibernate dialect in use is just a default one, but I'm not sure how to confirm this.
Please let me know if anyone has ideas about this.
P.S. As a practical matter, it would be useful for me if the script were generated with some sort of placeholder for the unrecognized data type. If I had a creation script with 48 columns correctly defined and 2 with "Undefined data type" then I could pretty easily fix it for this one-time creation script. Does it make sense to log this as an enhancement?
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
Squirrel-sql-users mailing list