[TYPO3-core] RFC #15457: Add support for prepared queries

Martin Kutschker masi-no at spam-typo3.org
Sun Aug 15 20:28:49 CEST 2010


Am 15.08.2010 09:54, schrieb Xavier Perseguers:
> 
>> i don't like the naming of stmt_execute (too cryptic abbreviation). Why
>> not preparedQuery_execute, or like the others exec_PREPAREDquery
> 
> Taken from MySQLi (http://ch.php.net/manual/en/mysqli-stmt.execute.php) but exec_PREPAREDquery is OK
> I guess.

At least it fits better to the current naming scheme of t3lib_db. In v5 it should probably be
executeStatement(), but we're talking about v4 here.

>> why choosing "thaw"? I looked up the translation but can't associate
>> what is meant.
> 
> :-) that was one of the point where I did not know which verb to choose. I took the naming from
> Extbase code where the data mapper "thaws" the property values onto an object. I understood it as
> some synonym of "merge" if you look a translation.

I think it's a metaphor. While the object is in the DB it is frozen, when retrieved back into memory
it will thaw (thaw means for a frozen object to get fluid). So IMHO it would be more natural to thaw
objects, but not properties. Anyway, it does not mean "merge". Perhaps "populate" or "fill in" are
more fitting.

Masi


More information about the TYPO3-team-core mailing list