I believe there are some limits on some
databases as to how many LONG VARCHAR columns exist. At least for DB2 (which
I know we don't officialy support, but I believe I've got it mostly working),
columns longer than 32k must be set as CLOB rather than VARCHAR. So I don't
have a problem with making the columns longer by default, but still think
some limits aren't too bad.
"Sergiu Dumitriu"
<sergiu.dumitriu@gmail.com>
02/28/2007 03:05 PM
Please respond to
xwiki-dev@objectweb.org
To
xwiki-dev@objectweb.org
cc
Subject
[xwiki-dev] Re: [Proposal] Some/All
fields in the database should be longer
5 days without an answer. So, everybody agrees?
On 2/23/07, Sergiu Dumitriu <sergiu.dumitriu@gmail.com
> wrote:
There are many properties stored in VARCHAR(255) fields,
which sometimes isn't enough. This already causes http://jira.xwiki.org/jira/browse/XWIKI-883
. Changing to variable length field doesn't have any major side effects,
as I know.
As pro arguments:
1. The size of the database will not increase
2. There are already some fields stored as mediumtext and longblob, so
it's not something new in the database
3. The fewer limits there are, the better
4. Issues like XWIKI-883 will be fixed
... and maybe more
Is there something I'm missing that prevents this?
-- http://purl.org/net/sergiu
--
You receive this message as a subscriber of the xwiki-dev@objectweb.org
mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws