On Tue, Jan 01, 2008 at 08:11:01PM +0000, Ion wrote: > Email address: [EMAIL PROTECTED]
lets hope Ion is subscribed! :) > I tested PostgreSQL 8.3 beta4 with tinyerp and I have this problem: > pg_catalog.substring(date, integer, integer) does not exist This is most likely a bug in tinyerp. substring has only ever been defined for string data types and isn't valid for date types at all. > I have not this problem with postgresql 8.2.5. Prior to PG 8.3, all types would be silently coerced into TEXT types in certain cases, leading to all sorts of strangeness. I've just downloaded the source of tinyerp and had a look though and this practice seems pretty endemic. They should really be using to_char(date_exp, 'YYYY-MM') instead of substring(date_exp FOR 7) in all their queries. Sam ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
