[TYPO3-project-4-3] fe_group SQL-statement, question out of curiosity

[Martin Kutschker]

Niels Fröhling schrieb:
> Xavier Perseguers wrote:
>> Hi,
>>
>>
>>> I'd like to know why actually the SQL statement for
>>> group-enableFields contains
>>> this condition this way:
>>>
>>> getMultipleGroupsWhereClause() :=
>>>
>>> AND (pages.fe_group='' OR pages.fe_group IS NULL OR
>>> pages.fe_group='0' OR
>>> (pages.fe_group LIKE '%,0,%' OR pages.fe_group LIKE '0,%' OR
>>> pages.fe_group LIKE
>>> '%,0' OR pages.fe_group='0') OR (pages.fe_group LIKE '%,-1,%' OR
>>> pages.fe_group
>>> LIKE '-1,%' OR pages.fe_group LIKE '%,-1' OR pages.fe_group='-1'))
>>>
>>> Is there a deeper reason, like an SQL-compatibility issue? Because
>>> this can be a
>>> single condition (per group to check for) with 'FIND_IN_SET' and
>>> 'FIELD':
>>
>> DBAL is part of core and it enables another DBMS than MySQL. For
>> instance Postgres or Oracle...
>>
> 
>  It seems listQuery/searchQuery are not overloaded in dbal, presumably
> this is not and issue of "not-allowed", but "not-done". Correct?

Not every function is and should be overloaded by DBAL. Basically only
t3lib_db (and some functions of the installer and EM) are and should be
handled by DBAL.

Masi