Thanks Mark. On one hand, I appreciate it, but on the other hand, nobody should use Transfer any longer. Hibernate is simply a better choice but for some of us who can't easily migrate away due to complexity, I'm trying to keep things at least relevant.
I realize in my title I teased "alternative data support" but didn't actually include anything. I updated my issue here with a list of all files and steps required to add more type support:
https://github.com/TransferORM/transfer/issues/10You may wonder, "what other types are there?" to which I would answer:
http://www.postgresql.org/docs/9.4/static/datatype.html boom!
Specifically I wanted to add the latest jsonb support so I could do dynamic user-defined "columns" in a nosql approach alongside my relational data but Postgres doesn't have a built-in varchar-to-jsonb cast. So, I needed to be able to use a <cfqueryparam cfsqltype="cf_sql_other" value="foo" />::jsonb
where that ::jsonb on the end causes the cast. I did it and have it working and all the files are listed in the issue but I haven't done it in a nice clean abstract way so I can't commit my work so far. My next test is to see if I can replace UUID with the native UUID type in Postgres which, instead of being a 35-character char is a 16-bit value (meaning storage and indexes are all about 50% of the size and therefore faster).
So, some progress, but still, use Hibernate if you can. :)
Brian