[TYPO3-dev] Problem with long strings in tt_content (Oracle)

ries van Twisk typo3 at rvt.dds.nl
Thu Dec 6 15:22:22 CET 2007


On Dec 6, 2007, at 8:44 AM, Moreno Feltscher wrote:

>> On PostgreSQL this can be mapped to text, can this also be true for
>> oracle?
>> Basically what I did is changed ALL varchars to text.
> Sounds nice. Are there any problem if you do this? If not, I think
> this would also be the solution for oracle (LONG (or BLOB?) instead of
> TEXT, which doesn't exist on Oracle).
> Anyway, where can I find the definition of which type is mapped to  
> which?
>
> Moreno

varchar or TEXT doesn't make a difference on PostgreSQL.

internally to PostgreSQL varchar(xx) is the same as TEXT but the varchar
as a constrain added to the length of the text. That's the only  
difference.
memory whise it doesn't make a difference, also not for indexing.

oracle might do the same?

Ries











More information about the TYPO3-dev mailing list