[Typo3-dev] t3lib_befunc::deleteClause
Kasper Skårhøj
kasper2005 at typo3.com
Wed Mar 23 13:43:45 CET 2005
I would like to hear what Karsten Dambekalns says about it. He knows
more about the inter-operability of databases than the rest of us
related to TYPO3/DBAL.
Ingmars point is still valid though: What about enableFields() and
potentially other functions that will use the table name for building
SQL? If making this patch to deleteClause() just opens up the door for
adding a new parameter to 10 core functions I rather not have it in any
of them!
- kasper
On Wed, 2005-03-23 at 11:50, Peter Niederlag wrote:
> Hi,
>
> Martin Kutschker schrieb:
> > "Michael Stucki" <michael at typo3.org> schrieb im Newsbeitrag
> > news:mailman.1.1111528466.26219.typo3-dev at lists.netfielders.de...
> >
> >>Ingmar Schlecht wrote:
> >>
> >>
> >>>Martin Kutschker wrote:
> [...]
> > Aliases are just shorthands for SQL-Queries:
> >
> > SELECT t1.somefield,t2.somefield FROM table_with_some_exteremely_long_name
> > AS t1, another_table_with_a_long name AS t2 WHERE ...
> >
> > It's just plain regular SQL. Why use a PHP workaround, if there's something
> > already there in SQL? AFAIK this is ANSI-SQL not Mysql-SQL, so no DBAL
> > issues here.
>
> I use aliases quite some times as well(FE-Plugins only yet). Actually I
> didn't spot any problems yet. Anyway I would support changes that are
> meant to fix some possible troubles in use with aliases.
>
> Cheers,
> Peter
--
- kasper
*******************
Happy new year! - My email address is now:
kasper2005 at typo3.com
More information about the TYPO3-dev
mailing list