[geeklog-devel] Geeklog Story Size Limits
geeklog at thehares.com
Sat Nov 24 22:06:33 EST 2007
When I looked at the schema for the MS-SQL database, upon first glance, it
appears to define story intro and body contents as VARCHAR(5000). Surely
that's not right, am I misreading the Schema in mssql_tableanddata.php?
I would have perhaps expected VARCHAR(65536) to be compatible with
current/past MySQL TEXT limits.
For SQL Server, perhaps we should be thinking about changing varchar() to
text and using full text search index instead? Having intro(5000) and
body(5000) already puts us over the 8060 byte row "limit" for updating.
Problem there is that it may work fine now, but fail later from what I
understand (but have not personally experienced). SQL Server 2005 may not
have quite the same soft 8060 byte row updating limit. It's possible I'm
wrong on this however as I'm not a seasoned SQL Server vet.
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Alexander
Sent: Saturday, November 24, 2007 2:09 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Story Size Limits
Dirk Haun wrote:
> Jeff Hare wrote:
>> What's the chance of bumping the story body type up to MEDIUMTEXT?
> I'd like to pass this question on to our database experts: What would be
> the downsides? Would it, for example, require more space even if not used?
While I'm not one of the DB experts ;-) my fat MySQL book (for MySQL 4)
and the online documentation at
for MySQL 5.1) tell me that the space requirements for MEDIUMTEXT are
minimal above TEXT.
To be precise it's 1 byte per entry!
With this you have room for 16.777.215 characters - not taking space
requirements for Unicode characters into account. These can take up to
three bytes space.
Other than that there doesn't seem to be a big downside.
Of course larger DB entries won't exactly lead to better performance,
but this is only in effect if one really uses that much space.
Apparently the current TEXT size with up to 65k chars is sufficient for
the average GL user. So these people shouldn't see or feel any
difference at all.
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel