You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quick story - trying to add BigInt into my app that uses Transfer on Postgres. Transfer universally uses cf_sql_float for all "numeric" types. This breaks bigint support. It's possible to add addtional metadata into transfer.xml and have it flow to the right place but I gave up on bigint support for other reasons. This is how you would do it if you wanted to support more exotic data types/matching.
I'm only concerned with at this point however this could be extended:
Fix the XSD to allow an additional attribute on properties called "sqltype"
In property.cfc, add methods get/setSqlType(), add setSqlType("") to init(), in setMemento(), add:
In transfer/com/sql/Query.cfc, add a third parameter to mapParam for "sqltype"
In transfer/com/sql/QueryExecution.cfc, in executeQuery(), add a check for block.mapparam.sqltype and branch accordingly for your native use. In my case, I used cf_sql_bigint if sqltype was "bigint"
In transfer/com/sql/TransferInserter.cfc, in buildInsertBasicQuery(), add the sqlType to the list of arguments passed like query.mapParam("property:" & property.getName(), property.getType(), property.getSqlType());
In transfer/com/sql/TransferUpdater.cfc, do the same thing in buildUpdateBasic()
I don't know that I'm planning to do this now but it was a PITA to figure out so I want to capture it here in case anyone wants to know how it would work.
The text was updated successfully, but these errors were encountered:
Quick story - trying to add BigInt into my app that uses Transfer on Postgres. Transfer universally uses cf_sql_float for all "numeric" types. This breaks bigint support. It's possible to add addtional metadata into transfer.xml and have it flow to the right place but I gave up on bigint support for other reasons. This is how you would do it if you wanted to support more exotic data types/matching.
I'm only concerned with at this point however this could be extended:
query.mapParam("property:" & property.getName(), property.getType(), property.getSqlType());
I don't know that I'm planning to do this now but it was a PITA to figure out so I want to capture it here in case anyone wants to know how it would work.
The text was updated successfully, but these errors were encountered: