#233
- Created on2009-12-08 14:56
- Reported by
- StatusNew
- PriorityNormal (3)
- Assigned to-
- Milestone-
- Plan Level-
- Due Date-
Feature-Request MetaMapper setObject overload without SQL.Type
The problem is that the current MetaMapper code always uses the overload of setObject
that takes the type parameter, and there is no type for, let's say PostgreSQL's CIDR, MAC, UUID, etc.. Types.
We could maybe add a flag or special Type that tells MetaMapper to use the setObject without the type, so it would be possible to use db-specific column types.
Best regards
that takes the type parameter, and there is no type for, let's say PostgreSQL's CIDR, MAC, UUID, etc.. Types.
We could maybe add a flag or special Type that tells MetaMapper to use the setObject without the type, so it would be possible to use db-specific column types.
Best regards
Leave a comment
(from fbettag on github) At the moment this works at least for creation. Add this into the MappedField block:
override def fieldCreatorString(dbType: DriverType, colName: String): String = colName+" CIDR"
I guess i have to play a bit more to get stuff like "<<" on CIDR working. Maybe i get this rudimentarily to work til there is a real solution :)
override def fieldCreatorString(dbType: DriverType, colName: String): String = colName+" CIDR"
I guess i have to play a bit more to get stuff like "<<" on CIDR working. Maybe i get this rudimentarily to work til there is a real solution :)