Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Odbc > Re: Access issu...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 2 of 3 Topic 2323 of 2403
Post > Topic >>

Re: Access issue again

by aklaver@[EMAIL PROTECTED] (Adrian Klaver) Mar 29, 2008 at 05:08 PM

On Saturday 29 March 2008 4:50 pm, Andreas wrote:
> Hi,
>
> whenever I ODBC link pg-tables into access I get this error in the log:
> It's translated by me so it won't be the original english error text.
> -----------------
> 2008-03-30 00:28:45 CET db_sales user1 WARNING:  not standardconform use
> of \\ in  characterstring at char 264
> 2008-03-30 00:28:45 CET db_sales user1 TIP:  Use the Syntax for
> Escape-strings for Backslashes, e.g. E'\\'.
> ------------------
>
> Besides this error the linked tables seem to work perfectly.
> Whats wrong here?

See this:

http://www.postgresql.org/docs/8.3/interactive/runtime-config-compatible.html

escape_string_warning (boolean)

    When on, a warning is issued if a backslash (\) appears in an ordinary

string literal ('...' syntax) and standard_conforming_strings is off. The 
default is on.

    Applications that wish to use backslash as escape should be modified
to 
use escape string syntax (E'...'), because the default behavior of
ordinary 
strings will change in a future release for SQL compatibility. This
variable 
can be enabled to help detect applications that will break. 

standard_conforming_strings (boolean)

    This controls whether ordinary string literals ('...') treat
backslashes 
literally, as specified in the SQL standard. The default is currently off,

causing PostgreSQL to have its historical behavior of treating backslashes
as 
escape characters. The default will change to on in a future release to 
improve compatibility with the standard. Applications can check this 
parameter to determine how string literals will be processed. The presence
of 
this parameter can also be taken as an indication that the escape string 
syntax (E'...') is sup****ted. Escape string syntax should be used if an 
application desires backslashes to be treated as escape characters. 

You can change the escape_string_warning to escape_string_warning=False in

postgresql.conf to suppress the messages.
-- 
Adrian Klaver
aklaver@[EMAIL PROTECTED]
 
Sent via pgsql-odbc mailing list (pgsql-odbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
 




 3 Posts in Topic:
Access issue again
maps.on@[EMAIL PROTECTED]  2008-03-30 00:50:09 
Re: Access issue again
aklaver@[EMAIL PROTECTED]  2008-03-29 17:08:04 
Re: Access issue again
maps.on@[EMAIL PROTECTED]  2008-03-30 03:00:18 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sat Sep 6 15:25:28 CDT 2008.