Manuel Lemos | 9 Mar 19:50
Picon
Favicon

[phpdba] Re: so who's there?

Hello,

on 03/08/2007 04:57 AM Lukas Kahwe Smith said the following:
>> Any particular reason why the list was not created on a more capable
>> list service, like Yahoo Groups, for instance?
> 
> Not really, well I guess I personally prefer this over the services of a
> large organization, where people have to create accounts.

Erm... in Yahoo groups you do not have to create accounts. You can just
subscribe and unsubscribe by e-mail. Accounts are only needed to access
Web resources associated to the group.

Maybe you were thinking of Google Groups. If there is a thing that
Google does not lead yet, it is in the mailing lists/discussion groups
field.

>>> However, over time I guess this list will hopefully will define itself
>>> as we discuss topics that come up. So with that I encourage all of you
>>> to post about challenging new features you are currently working on.
>>
>> I am not working in any new feature for Metabase right now. The last
>> feature that I developed, as you know was the pattern matching
>> abstraction. It is still not perfectly solved because different
>> databases may handle patterns with case sensitiveness or not. I have not
>> invested time in finding a solution either.
> 
> Yeah, I remember. One thing that we found out back then is that we would
> probably write a callback for SQLite IIRC:

(Continue reading)

Torsten Raudssus | 12 Mar 10:37
Picon
Favicon

Re: [phpdba] Re: so who's there?

Hiho,
> I was not thinking of SQLite. I was thinking that MySQL LIKE operator is
> case insensitive (which is what most people want) but in other databases
> LIKE is case sensitive by default.
>
>   

Aehm.... = is also case-insensitive..... i did in my ORM that you got 
$obj->BinaryMatch(true/false) which adds BINARY to the comparing or not....

Bye!

Manuel Lemos | 13 Mar 06:08
Picon
Favicon

Re: [phpdba] Re: so who's there?

Hello,

on 03/12/2007 06:37 AM Torsten Raudssus said the following:
> Hiho,
>> I was not thinking of SQLite. I was thinking that MySQL LIKE operator is
>> case insensitive (which is what most people want) but in other databases
>> LIKE is case sensitive by default.
>>
>>   
> 
> Aehm.... = is also case-insensitive..... i did in my ORM that you got
> $obj->BinaryMatch(true/false) which adds BINARY to the comparing or not....

If you read my original message again, you may notice that I am talking
about other databases like Oracle for instance, on which  comparison and
 pattern matching is case sensitive.

I have already thought of having a switch function like you suggest that
would trigger case sensitive options, but I am afraid it would probably
not work very well in all databases.

I think Oracle has a per connection option to toggle case sensitiviness,
but I think that applies to the whole queries. If you can a WHERE clause
with multiple conditions, and in some you want to be case sensitive and
others be case insensitive, a per connection option will not work.

--

-- 

Regards,
Manuel Lemos
(Continue reading)

Lukas Kahwe Smith | 9 Mar 21:43

Re: [phpdba] Re: so who's there?

Manuel Lemos wrote:

>> Yeah, I remember. One thing that we found out back then is that we would
>> probably write a callback for SQLite IIRC:
> 
> I was not thinking of SQLite. I was thinking that MySQL LIKE operator is
> case insensitive (which is what most people want) but in other databases
> LIKE is case sensitive by default.

Not sure how you did in Metabase, but in MDB2 I have the following code 
for this:
             switch ($operator) {
             // case insensitive
             case 'ILIKE':
                 $match = $field.'LIKE ';
                 break;
             // case sensitive
             case 'LIKE':
                 $match = $field.'LIKE BINARY ';
                 break;

Not sure if I would use "ILIKE" again, probably I would use like with an 
optional attribute to flag case sensitivity.

> If you want an honest opinion, I am afraid that goal will hardly happen,
> I mean most people will not share good ideas.

You know me. I am an optimist willing to invest time :)

> There is something good that worked very well in the Java world: JCP -
(Continue reading)

Manuel Lemos | 13 Mar 04:55
Picon
Favicon

Re: [phpdba] Re: so who's there?

Hello,

on 03/09/2007 05:43 PM Lukas Kahwe Smith said the following:
> Manuel Lemos wrote:
> 
>>> Yeah, I remember. One thing that we found out back then is that we would
>>> probably write a callback for SQLite IIRC:
>>
>> I was not thinking of SQLite. I was thinking that MySQL LIKE operator is
>> case insensitive (which is what most people want) but in other databases
>> LIKE is case sensitive by default.
> 
> Not sure how you did in Metabase, but in MDB2 I have the following code
> for this:
>             switch ($operator) {
>             // case insensitive
>             case 'ILIKE':
>                 $match = $field.'LIKE ';
>                 break;
>             // case sensitive
>             case 'LIKE':
>                 $match = $field.'LIKE BINARY ';
>                 break;
> 
> Not sure if I would use "ILIKE" again, probably I would use like with an
> optional attribute to flag case sensitivity.

If I am not mistaken in Oracle, MS SQL, LIKE is case sensitive. I did
not find any other database that supports LIKE BINARY either.

(Continue reading)

Lukas Kahwe Smith | 13 Mar 06:58

Re: [phpdba] Re: so who's there?

Manuel Lemos wrote:

>> Not sure how you did in Metabase, but in MDB2 I have the following code
>> for this:
>>             switch ($operator) {
>>             // case insensitive
>>             case 'ILIKE':
>>                 $match = $field.'LIKE ';
>>                 break;
>>             // case sensitive
>>             case 'LIKE':
>>                 $match = $field.'LIKE BINARY ';
>>                 break;
>>
>> Not sure if I would use "ILIKE" again, probably I would use like with an
>> optional attribute to flag case sensitivity.
> 
> If I am not mistaken in Oracle, MS SQL, LIKE is case sensitive. I did
> not find any other database that supports LIKE BINARY either.

Yeah, of course .. I expect that this is actually the standard. 
PostgreSQL is also case sensitive by default. They "invented" the ILIKE 
for case insensitive LIKE.

regards,
Lukas


Gmane