[Typo3-dev] System Extensions, part II

[Martin Kutschker]

Hi!

Of course MAX_INT is db specific. In fact it is column-type specific. 
Depending on the chosen type (int, smallint, int4 or whatever) MAX_INT will 
be different. It'd be up to DBAL to report a meaningful value for the given 
table.

Masi

"Michael Stucki" <michael at typo3.org> schrieb im Newsbeitrag 
news:mailman.1.1110322624.28148.typo3-dev at lists.netfielders.de...
Hello Masi,

> Kasper Skårhøj wrote:
>> The problem is that when versions are swapped the introduction of a
>> temporary negative uid will set the internal "next autoindex" to some 2
>> billions.
>
> How about using MAX_INT instead of -1 as temporary value. Or do you need
> more than one value at given time?

Guess that's a very old mail I still had on my pending messages list. I see
you never got a reply. Do you think it could solve any problems with
versioning?

If MAX_INT is MySQL-specific then better forget this quickly...

- michael
-- 
Want support? Please read the list rules first: http://typo3.org/1438.0.html