On 26/01/17 11:12, Josh Lavin wrote:
> commit e287246f93151bc165fa8d431997eba5d5a1bb8f
> Author: Josh Lavin <digory@cpan.org>
> Date: Wed Jan 25 14:12:30 2017 -0800
>
> Use timestamp datatype for Postgres
> -Database userdb COLUMN_DEF "mod_time=varchar(20)"
> +Database userdb COLUMN_DEF "mod_time=timestamp"
> -Database userdb PREFER_NULL usernick
> +Database userdb PREFER_NULL usernick mod_time
Be careful with this. I recall having problems with timestamp in the
past where Interchange would try to truncate the input string based on
the bitwidth of the data type and it would cause the whole thing to fail.
Peter
_______________________________________________
interchange-users mailing list
interchange-users@icdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchange-users
> commit e287246f93151bc165fa8d431997eba5d5a1bb8f
> Author: Josh Lavin <digory@cpan.org>
> Date: Wed Jan 25 14:12:30 2017 -0800
>
> Use timestamp datatype for Postgres
> -Database userdb COLUMN_DEF "mod_time=varchar(20)"
> +Database userdb COLUMN_DEF "mod_time=timestamp"
> -Database userdb PREFER_NULL usernick
> +Database userdb PREFER_NULL usernick mod_time
Be careful with this. I recall having problems with timestamp in the
past where Interchange would try to truncate the input string based on
the bitwidth of the data type and it would cause the whole thing to fail.
Peter
_______________________________________________
interchange-users mailing list
interchange-users@icdevgroup.org
http://www.icdevgroup.org/mailman/listinfo/interchange-users