On 11/8/05, Ian Bicking <[EMAIL PROTECTED]> wrote:
You can put an index on a TEXT column in MySQL, but the index has to define a length.
So now I'm getting spooked: using "length" generates a fixed width column, vs. VARCHAR? For some daft reason, I'd been going under the idea that using "length" gave you VARCHAR, and no length gave you the approriate BLOB-ish type (TEXT for MySQL, etc). Oracle still has 4K limits on VARCHAR, for example...
Roger
>
>
> As you say, MySQL is the killer there. If the length column isn't in
> it complains to high heaven. Although, doesn'y MySQL have a TEXT
> column type? I wonder if it would be possible to have SQLObject
> automatically create a TEXT column if you don't specify a length in a
> StringCol?
It does. The only issue I know of is that you can't put an index on
such a column. Silly, really, as it would be perfectly fine to only
index the first 255 characters and ignore the rest. But oh well. Or
maybe you just couldn't put an index on BLOB columns? Now I can't
remember; it came up in the SQLObject bug tracker recently, mostly
because MySQL gives a weird and confusing error message when it happens.
You can put an index on a TEXT column in MySQL, but the index has to define a length.
So now I'm getting spooked: using "length" generates a fixed width column, vs. VARCHAR? For some daft reason, I'd been going under the idea that using "length" gave you VARCHAR, and no length gave you the approriate BLOB-ish type (TEXT for MySQL, etc). Oracle still has 4K limits on VARCHAR, for example...
Roger
