From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | Scott Frankel <leknarf(at)pacbell(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: storing windows path strings |
Date: | 2010-01-29 23:00:11 |
Message-ID: | e94e14cd1001291500l501bd7edv1e16b8f5363c4cb7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2010/1/29 Scott Frankel <leknarf(at)pacbell(dot)net>:
>
> Hi all,
> What's the proper way to store directory path strings in a table, especially
> ones with backslashes like windows?
> I'm currently using a prepared statement with bind value. Do I need to
> pre-parse all user entries to identify any backslash characters before
> passing the string to my insert statement?
> Searches through the documentation turned up references
> to escape_string_warning (boolean) and standard_conforming_strings
> (boolean). I'm not sure I'll have access to server side config.
> Thanks in advance!
> Scott
>
> eg:
> CREATE TABLE foo (
> foo_id SERIAL PRIMARY KEY,
> name VARCHAR(32) UNIQUE NOT NULL,
> dirpath text DEFAULT NULL);
>
> INSERT INTO foo (name, dirpath) VALUES ('bar', 'c:\windows\path\to\bar');
> --> WARNING: nonstandard use of \\ in a string literal
explicetely set ON the standard_conforming_string in the postgresql.conf
*but* take care it don't break your application.
INSERT INTO foo (name, dirpath) VALUES ('bar', 'c:\windows\path\to\bar');
>
>
>
>
--
Cédric Villemain
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2010-01-29 23:43:33 | Re: Behavior of "at time zone" |
Previous Message | Scott Frankel | 2010-01-29 22:42:06 | storing windows path strings |