DataMapper ORM v1.8.0

[eluser]Basketcasesoftware[/eluser]
[quote author="WanWizard" date="1297054544"]Are you using the latest version? There should be no reference to OverZealous' website since I've taken over. Download the tip from http://bitbucket.org/wanwizard/datamapper to be sure. Or use the online user guide at http://datamappper.wanwizard.eu.

There is no default ordering, queries return data in whatever order your database will present them if you don't include an ORDER BY clause in your query.

Messaging is complex business, especially if you're buiding for scale. What I've done for a CMS I'm working on is to create the indices as nested trees (in my case forums, threads and PM's), and made sure the records are fixed length. The message text itself is in a separate table, linked to by the id, together with specific message attributes like author, timestamps, etc. This will also allow the message to appear in multiple places.

You can use Datamapper's nested sets extension, which works pretty ok for standard nested set constructions. It's documented in the user guide.[/quote]

I'm using the current version. Or so I thought. No biggie.
The messenging I'm working on is the users' private mail boxes (PMs). I'm trying to allow them to organize their received messages in folders and sub-folders. I realized I needed nested trees towards the end of my last post. What records are you keeping as a fixed length?
I am keeping the messaging table separate with date, author, subject, etc. I'm keeping the subject length to 120 characters (I borrowed that figure from your examples. Seemed a reasonable suggestion).

So far I've broken things down into three tables: Folders, Threads, and Messages.
folder: has_one 'account' (I suspect I need more here).
thread: has_many 'folder' 'message'
message: has_one 'thread' 'creator'
has_many 'contributor'