Re: BUG #3848: function pg_catalog.substring(date, integer, integer) does not exist - Mailing list pgsql-bugs

From Sam Mason
Subject Re: BUG #3848: function pg_catalog.substring(date, integer, integer) does not exist
Date
Msg-id 20080101213941.GD11262@frubble.xen.chris-lamb.co.uk
Whole thread Raw
In response to Re: BUG #3848: function pg_catalog.substring(date, integer, integer) does not exist  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Jan 01, 2008 at 04:29:47PM -0500, Tom Lane wrote:
> Sam Mason <sam@samason.me.uk> writes:
> > 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.
>
> Or at least explicitly casting the date to text.  But your way is
> better, since it won't break if the datestyle is something other
> than ISO.

It also improves code readability is is always a good thing.

I've just gone though the code and sent a patch to the tinyerp-devel
list with these fixes in.  Lets see if it gets incorporated.


  Sam

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3848: function pg_catalog.substring(date, integer, integer) does not exist
Next
From: "Mark Reid"
Date:
Subject: Re: BUG #3847: plpython trigger caches table structure - doesn't see new / changed columns