Thanks.
On 6/1/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Scott Klarenbach <[EMAIL PROTECTED]> wrote on 05/27/2005 06:57:19
> PM:
>
>
> > -- How is 'xFxIxExLxDx1x' easier to search than 'FIELD1'?
> >
> > It's not easier. It is; however, accurate for the purpose at hand.
> > FIEL
Scott Klarenbach <[EMAIL PROTECTED]> wrote on 05/27/2005 06:57:19
PM:
> -- How is 'xFxIxExLxDx1x' easier to search than 'FIELD1'?
>
> It's not easier. It is; however, accurate for the purpose at hand.
> FIELD1 isn't completely inclusive...it would miss FIELD-1...
>
> -- However, It seems to m
-- How is 'xFxIxExLxDx1x' easier to search than 'FIELD1'?
It's not easier. It is; however, accurate for the purpose at hand.
FIELD1 isn't completely inclusive...it would miss FIELD-1...
-- However, It seems to me that this kind of data manipulation
(cleanup) needs to happen BEFORE the data ente
Scott Klarenbach <[EMAIL PROTECTED]> wrote on 05/27/2005 04:38:40
PM:
> Ya, it is a little too specific...here's why I need it.
>
> I have a client that wants to search for part numbers in his DB. The
> problem is, they come into his DB from external sources, with all
> sorts of special charact
Ya, it is a little too specific...here's why I need it.
I have a client that wants to search for part numbers in his DB. The
problem is, they come into his DB from external sources, with all
sorts of special characters in them...
So, he has fields like
field_one!,
fi--eld 2,
@fi#eld__3xxx
e
I'm working on a set of UDFs for preg functions.
[EMAIL PROTECTED] wrote:
I have a hard time figuring out when you would use such a function. I do
not believe you will be able to duplicate this behavior without
constructing your own UDF or by writing a stored procedure. BTW, why *do*
you wan
I have a hard time figuring out when you would use such a function. I do
not believe you will be able to duplicate this behavior without
constructing your own UDF or by writing a stored procedure. BTW, why *do*
you want this function?
Shawn Green
Database Administrator
Unimin Corporation - Spru
Here's what I came up with in case anyone else needs a quick fix. A
regular expression replace would've been nicer, but, you do what you
gotta do...
CREATE PROCEDURE `test`(`par` varchar(60))
BEGIN
DECLARE nChars INT DEFAULT CHAR_LENGTH(par);
DECLARE nCounter INT DEFAULT 1;
I'm trying to replicate this PHP behavior in a MySQL stored procedure.
The purpose is to pad every character of the string with a pad
character. For example, if the pad character is 'x' and the string is
'STRING', the result is 'xSxTxRxIxNxGx'.
Here is the PHP code if it helps. I'd like to use
