[TYPO3-dev] unexistent GLOBALS return NULL instead of ""

[Popy]

It's a well known behaviour : undefined variable is null and throws a
NOTICE error.
The UPDATE/INSERT helpers now detects NULL values instead of casting them
to strings, so they are now inserting the values you ask. And you are
asking the wrong value.


Cordialement,
Pierre Dudoret


2014/1/21 Thomas Sperling <moppie.mop at gmx.de>

> Hello,
> currently I upgrade a TYPO3-System up to 6.2dev.
> I got several Errors like: "ERROR       Column 'cruser_id' cannot be null
> lastBuiltQuery  INSERT INTO sys_file_metadata (file,pid,crdate,tstamp,cruser_id)
> VALUES ('2258','0','1390303717','1390303717',NULL)"
> OR
> "Column 'cookie' cannot be null
> lastBuiltQuery  INSERT INTO index_stat_search (searchstring,searchoptions,
> feuser_id,cookie,IP,hits,tstamp) VALUES ('test',...,...,NULL,.....)
>
> In the problem is that an empty $this->fe_user->id and a empty
> $GLOBALS['BE_USER']->user['uid'] result into NULL and not in an empty
> string. Is this a bug, does someone know this problem?
>
> Regards,
> Thomas
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>