At 4:01 +0200 10/8/04, Przemyslaw Popielarski wrote:
Paul DuBois <[EMAIL PROTECTED]> wrote:
SELECT
@a:=FIRMLEGALZIPCODE
FROM tCustomers
WHERE @a REGEXP "[0-9]"
-> Empty set (0.03 sec)
You're expecting the value to be selected first so that you then can
test it with the WHERE clause later.
Paul DuBois <[EMAIL PROTECTED]> wrote:
>> SELECT
>>@a:=FIRMLEGALZIPCODE
>> FROM tCustomers
>> WHERE @a REGEXP "[0-9]"
>> -> Empty set (0.03 sec)
>
> You're expecting the value to be selected first so that you then can
> test it with the WHERE clause later.
Of course you're right. Thanks. Accor
At 3:47 +0200 10/8/04, Przemyslaw Popielarski wrote:
Paul DuBois <[EMAIL PROTECTED]> wrote:
User variables do not work with REGEXP under MySQL 4.0.21 & 4.1.5.
Is this a bug or a feature?
It's difficult to provide an answer to this because you're providing
no information about what "do not work"
Paul DuBois <[EMAIL PROTECTED]> wrote:
>> User variables do not work with REGEXP under MySQL 4.0.21 & 4.1.5.
>> Is this a bug or a feature?
>
> It's difficult to provide an answer to this because you're providing
> no information about what "do not work" means. Can you be more
> specific?
Sure.
At 3:12 +0200 10/8/04, Przemyslaw Popielarski wrote:
User variables do not work with REGEXP under MySQL 4.0.21 & 4.1.5.
Is this a bug or a feature?
It's difficult to provide an answer to this because you're providing
no information about what "do not work" means. Can you be more specific?
mysql> s
User variables do not work with REGEXP under MySQL 4.0.21 & 4.1.5.
Is this a bug or a feature?
--
./ premax
./ [EMAIL PROTECTED]
./ koniec i bomba, a kto czytal ten traba. w.g.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.c