On Wed, 4 Apr 2007, Postgres User wrote:
Oleg,
This looks like a great module, do you have a pointer to it in English?
unfortunately, no.
If can send this module to me as a compressed file, I'll take the time
to post it on PgFoundry as a new project that everyone can easily
access and down
Oleg,
This looks like a great module, do you have a pointer to it in English?
If can send this module to me as a compressed file, I'll take the time
to post it on PgFoundry as a new project that everyone can easily
access and download.
Paul- if you go with the lower() edits route, be sure to no
Paul,
we have contrib module mchar, which does what you need. We developed it
when porting from MS SQL one very popular in Russia accounting software.
It's available from http://v8.1c.ru/overview/postgres_patches_notes.htm,
in Russian. I don't rememeber about license, though.
Oleg
On Wed, 4 Ap
> 2.) The Like function in SQL Server is case insensitive, PG it is case
> sensitive. The ilike function is not recognised by Access and it tries
> to turn that into a string, making my test (like "ilike 'blah'")
>
> Has anyone had any experience with moving an access program from SQL
> server
Klint Gore <[EMAIL PROTECTED]> writes:
> Is there any way to create operators to point like to ilike? There
> doesn't seem to be a like or ilike in pg_operator (not in 7.4 anyway).
Actually it's the other way 'round: if you look into gram.y you'll see
that LIKE is expanded as the operator ~~ and
Edward Macnaghten wrote:
Joshua D. Drake wrote:
You could preface all your queries with something like:
select * from foo where lower(bar) = lower('qualifer');
But that seems a bit silly.
And also it would prevent the optimizer from using any indexes on
"bar". Not a good idea.
You could
Paul Lambert <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> That could be attacked in a few ways, depending on whether you want
>> all text comparisons to be case-insensitive or only some (and if so
>> which "some").
> I don't have any case sensitive data - so if sensitivity could be
> completel
Paul Lambert wrote:
I've got an MS Access front end reporting system that has previously
used MS SQL server which I am moving to Postgres.
The front end has several hundred if not thousand inbuilt/hard-coded
queries, most of which aren't working for the following reasons:
1.) Access uses doubl
Joshua D. Drake wrote:
You could preface all your queries with something like:
select * from foo where lower(bar) = lower('qualifer');
But that seems a bit silly.
Joshua D. Drake
I'm trying to avoid having to alter all of my queries, per the OP I've
got several hundred if not thousands
On Tue, 03 Apr 2007 18:24:00 -0700, "Joshua D. Drake" <[EMAIL PROTECTED]> wrote:
> Paul Lambert wrote:
> > Tom Lane wrote:
> >> Paul Lambert <[EMAIL PROTECTED]> writes:
> >>> or the case sensitivity?
> >>
> >> That could be attacked in a few ways, depending on whether you want
> >> all text compari
Joshua D. Drake wrote:
You could preface all your queries with something like:
select * from foo where lower(bar) = lower('qualifer');
But that seems a bit silly.
And also it would prevent the optimizer from using any indexes on
"bar". Not a good idea.
Eddy
---(e
Paul Lambert wrote:
I've got an MS Access front end reporting system that has previously
used MS SQL server which I am moving to Postgres.
Are you using "PassThrough" queries? It is not clear
The front end has several hundred if not thousand inbuilt/hard-coded
queries, most of which are
Paul Lambert wrote:
Tom Lane wrote:
Paul Lambert <[EMAIL PROTECTED]> writes:
Is there any way to change the text qualifier in PG
No. I suppose you could hack the Postgres lexer but you'd break
pretty much absolutely everything other than your Access code.
or the case sensitivity?
That
Paul Lambert wrote:
I've got an MS Access front end reporting system that has previously
used MS SQL server which I am moving to Postgres.
The front end has several hundred if not thousand inbuilt/hard-coded
queries, most of which aren't working for the following reasons:
1.) Access uses doubl
Tom Lane wrote:
Paul Lambert <[EMAIL PROTECTED]> writes:
Is there any way to change the text qualifier in PG
No. I suppose you could hack the Postgres lexer but you'd break
pretty much absolutely everything other than your Access code.
or the case sensitivity?
That could be attacked in
Paul Lambert <[EMAIL PROTECTED]> writes:
> Is there any way to change the text qualifier in PG
No. I suppose you could hack the Postgres lexer but you'd break
pretty much absolutely everything other than your Access code.
> or the case sensitivity?
That could be attacked in a few ways, dependin
I've got an MS Access front end reporting system that has previously
used MS SQL server which I am moving to Postgres.
The front end has several hundred if not thousand inbuilt/hard-coded
queries, most of which aren't working for the following reasons:
1.) Access uses double quotes ("") as text
17 matches
Mail list logo
