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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: storing windows path strings


  • From: Scott Frankel <leknarf(at)pacbell(dot)net>
  • To: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
  • Cc: pgsql-general(at)postgresql(dot)org
  • Subject: Re: storing windows path strings
  • Date: Fri, 29 Jan 2010 16:23:56 -0800
  • Message-id: <09F2B617-D557-4D41-853D-F39CCBDCDED1@pacbell.net> <text/plain>


Excellent!  Mild testing so far, but it seems to work.  Thanks!
Scott




On Jan 29, 2010, at 3:00 PM, Cédric Villemain wrote:

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




Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group