On our organization we are porting an old, internally developed app,
that use Informix (SE 7.XX, on a sun box) as database backend and Gupta
Centura Team Developer 1.5.1 as development environment.
Centura uses Informix via a native driver, for postgres we pass along
odbc. Our postgres
Marco Gaiarin wrote:
On our organization we are porting an old, internally developed app,
that use Informix (SE 7.XX, on a sun box) as database backend and Gupta
Centura Team Developer 1.5.1 as development environment.
Centura uses Informix via a native driver, for postgres we pass along
odbc. Our
O Marco Gaiarin Sep 22, 2004 :
On our organization we are porting an old, internally developed app,
that use Informix (SE 7.XX, on a sun box) as database backend and Gupta
Centura Team Developer 1.5.1 as development environment.
Centura uses Informix via a native driver, for postgres we
Marco,
Centura uses Informix via a native driver, for postgres we pass along
odbc. Our postgres environment are a set of intel box, loaded with
debian woody, so postgres 7.2.1.
You do realize that this is a 2-year-old version of Postgresql, yes? It seems
to me that if you're going to take
I used the following SQL code to match '\foo\bar'
SELECT text FROM test WHERE text LIKE 'foo%'
But if I choose to use string comparison, instead of 4 escape characters, I
only need 2.
SELECT text FROM test WHERE text = '\\foo\\bar'
Why is that?
I am using PostgreSQL 7.4, and the SQL code
Wei Weng [EMAIL PROTECTED] writes:
But if I choose to use string comparison, instead of 4 escape characters, I
only need 2.
Why is that?
Backslash is an escape character for LIKE.
regards, tom lane
---(end of
Tom Lane wrote:
Wei Weng [EMAIL PROTECTED] writes:
But if I choose to use string comparison, instead of 4 escape characters, I
only need 2.
Why is that?
Backslash is an escape character for LIKE.
regards, tom lane
What about in regular strings? I do need to use
