Skip site navigation (1) Skip section navigation (2)

Re: Documentation for jdbc escapes

From: "Xavier Poinsard" <xpoinsard(at)free(dot)fr>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Documentation for jdbc escapes
Date: 2005-01-25 09:50:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
I updated the my documentation attempt with your remarks and added 
mention for escape char escape.

Kris Jurka wrote:
> If you are soliciting general comments it would help to make it available 
> in a more accessible format:

> For general feedback it seems a little too table oriented with not enough 
> accompanying text.  Describing what the argument reordering and duplicate 
> problem actually is would be helpful.  Also an example including Java code 
> would help the understanding process of how to actually call these 
> functions.  Mentioning Connection.nativeSQL() seems appropriate.


> In terms of specific feedback:
>  - it should mention outer join escapes
>  - the translation of dayname is in the wrong column (Table 1.3)
>  - The comments should be full sentences, starting with a capital letter
>    ending with a period.
>  - Section titles should get some captialization.
>  - Provide html link to referenced JDBC Technology guide
>  - A number of typos/grammatical errors:
>    - First paragraph
>      - of of
>      - had to specify way -> had to speciy a way
>    - Second section (escaped scalar functions)
>      - tables are showing -> tables show
>      - The driver support -> The driver supports
>      - specification describe the -> specification describes the

Attachment: escaped.xml.gz
Description: application/x-gzip (3.3 KB)

In response to


pgsql-jdbc by date

Next:From: Jean-Pierre PelletierDate: 2005-01-25 14:46:43
Subject: Re: setObject on PGInterval throws "Unknown Type null"
Previous:From: Xavier PoinsardDate: 2005-01-25 09:47:34
Subject: Patch for escaped escape char

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group