Hi Shelby,

I don't think the problem isn't with the backslashes. They are escaped and
seem to be working fine e.g. to insert a backslash in Access I had to use
one escape character ('\\') whereas in PostgreSQL four backslashes ('\\\\')
are required. The line that inserts the % is as follows...

      String aPath = group.getPath() + aOldGroupName + "\\%";

It just doesn't seem to be having the same effect in PostgreSQL as in
Access.



B

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shelby Cain
Sent: 11 March 2005 17:32
To: William Shatner; [EMAIL PROTECTED];
pgsql-general@postgresql.org; pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] [GENERAL] MS Access to PostgreSQL

--- William Shatner <[EMAIL PROTECTED]> wrote:
> I have recently migrated from MS Access to
> PostgreSQL.Previously I had
> a SQL command
> 
>       ResultSet aGroupResultSet =
> aGroupPathStmt.executeQuery(
>           "SELECT \"groupID\",\"fullpath\" FROM
> \"groups\" WHERE
> \"fullpath\" Like '" +
>           aPath + "'");
> 
> 
> 
> where aPath was equal to  'folder\another folder\%'.
> 
> The field to be edited stores the full path in the
> format
> 'folder\folder1\folder2' and so on...
> The purpose being to change all groups at this level
> of the
> hieracarchy and below, this was achieved using the
> '%' in Access, this
> however doesn't seem to work in PostgreSQL, it
> doesn't error out but
> it just seems to see the '%' as a normal character.
> 
> How can this be done in PostgreSQL?
> 

I suspect that, unlike Access, PostgreSQL will
intrepret C-style escape sequences (ie: \r, \n, \t) so
you'll need to properly escape the backslash in aPath
like so:

folder1\\folder2\\folder3

Regards,

Shelby Cain


                
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to