http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692007-07-02T09:05:56ZTYPO3 ForgeTYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454672007-07-02T09:05:56ZDmitry Dulepov
<ul></ul><p>You should use a checkbox like this:</p>
<p><checkbox>1000</checkbox></p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454682007-07-04T20:46:54ZGeorg Ringer
<ul></ul><p>This still doesn'T solve the problem because the value is optional and so 1000 as default is not an option</p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454692007-07-05T09:34:09ZDmitry Dulepov
<ul></ul><p>So, what do you want to have in the database if not 0 or 1000? How did you define field in SQL? By default it is NOT NULL DEFAULT '0'.</p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454702007-07-05T09:49:54ZGeorg Ringer
<ul></ul><p>It is just inside of flexforms and the best thing would be just nothing stored. Of course I could make 0 as default value and catch this inside my extension but the better way would be just nothing</p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454712007-07-05T09:51:21ZDmitry Dulepov
<ul></ul><p>You set evaluation to int. In PHP empty integer values evaluate to 0...</p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454722007-07-05T09:58:15ZGeorg Ringer
<ul></ul><p>ok, so please close this or delete it and thx for explanation</p> TYPO3 Core - Bug #17428: Eval => int will create '0' as value which is wronghttp://forge.typo3.org/issues/17428?journal_id=454732007-07-16T23:23:27ZMartin Kutschker
<ul></ul><p>I'm closing it on request, but of course Georg is right, the behaviour is dull. The problem is that the TCA doesn't distinct between field type (eg string, integer), input value transformation (eg md5) and value validation (eg range)</p>