[TYPO3-core] RFC: feature #16371: support for mysql_fetch_object to retreive a record as a model object

Jeff Segars jsegars at alumni.rice.edu
Thu Nov 18 00:49:44 CET 2010


On 11/15/10 8:28 AM, Lieuwe Hummel wrote:
> On 15-11-2010 13:27, Martin Kutschker wrote:
>>
>> Shouldn't the class name be resolved by
>> t3lib_div::makeInstanceClassName() first? If yes, this means
>> the deprecation of that function must be revoked.
>>
>> Masi
>
> Hi Masi
>
> There's another method: t3lib_div::getClassName($className), which is
> not deprecated, but is protected in stead of public.
>
> I see a couple of options:
> - leave it as it is; not desired as it leaves out XClass functionality
> - Undeprecate t3lib_div::makeInstanceClassName(), or make
> t3lib_div::getClassName() public
> - implement a getClassName() in t3lib_db; IMHO not desired as it is
> not consistent, i.e. same kind of functionallity on multiple places
>
> Any suggestions on which option to choose? Am i missing an alternative?
>
> NB: I found http://bugs.typo3.org/view.php?id=10497 to be related.
>
> Lieuwe

My vote would be to see t3lib_div::getClassName become public.  I'm +1 
to the overall idea, but would like to hear from Xavier on any DBAL 
implications also.

Thanks,
Jeff


More information about the TYPO3-team-core mailing list