what do you mean by "flattened version of the comment table"? are you
talking about table partitioning? because the comment table is flat,
there is only a single roller_comment table which maintains a single
reference back to the weblog entry the comment is associated with.
weblog ids are not numerical because the key generator happens to use a
alphanumerics when generating the hash. this isn't a requirement
really, just how it happens to work. i have never seen a real problem
with this, but if you think you'll see a significant benefit from using
purely numerical keys you can change it.
starting in Roller 4.0 there is a custom UUIDGenerator class which
provides a single generateUUID() method that all persisted classes use
to generate their ids. the default behavior is to use the
java.util.UUID class for generating the ids, but you can reimplement
that however you like so long as the ids are unique. That class is part
of the "core" component, so grab the src code and under components/core
you'll see the code. once you are done just rebuild that
roller-core.jar file and put it into your build of the application.
-- Allen
Milo wrote:
Our biggest problem is the amount of comments we have. We have solved
this by:
- creating a flattened version of the comment table and updating this
table wih triggers (MySQL5)
- writing new models and macros that replace the current macros that
query the original comment table
A blog page with many comments which would not load at all now loads in
an acceptable time period.
Why are the website ids not numerical?
Cheers
