From: | Chris <dmagick(at)gmail(dot)com> |
---|---|
To: | Joris Dobbelsteen <Joris(at)familiedobbelsteen(dot)nl> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: More formal definition of functions in documentation |
Date: | 2008-02-25 06:36:17 |
Message-ID: | 47C261E1.7020603@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joris Dobbelsteen wrote:
> Dear,
>
> I'm currently reading through the Postgresql documentation about how
> several functions work and which ones I would need. So far the
> documentation is great and well-structured!
>
> Unfortunally I'm not sure what functions will actually do when some
> non-obvious input is provided (which is sometimes required, as we cannot
> assume structure of the input at all times). A simple example is
> substring(text from 'blaat#"%#"' for '#')
> where text is not in the format of the regular expression, e.g. when
> text = 'text'. I don't know if the SQL standard includes such
> requirements, but documenting such behaviour might be a good addition to
> the help.
> If I know how and how to structure it, I'm willing to do some effect.
>
> In any case, something as already done for CREATE TABLE and such
> constructs are very good and well-defined.
Join the -docs list:
http://archives.postgresql.org/pgsql-docs/
and they'll be able to get you started :)
--
Postgresql & php tutorials
http://www.designmagick.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart Brooks | 2008-02-25 06:57:29 | autovacuum not freeing up unused space on 8.3.0 |
Previous Message | Tom Lane | 2008-02-25 06:19:50 | Re: reindexing |