Drew,
My first thought is: What is keeping you from adding these fields yourself by hand? Drew Morris wrote:
I would like to propose a couple of additions to the mailboxes table that would make the processing more efficient both for DBMAIL and for applications that share the data (like web front-ends). 1) Add a "Display Name" field to avoid having to parse it out of the name field if it is a subfolder
this doesn't add anything for IMAP.
2) Add a parentid field to store which folder it is a direct child of (use 0 for none)
this would make sense if imap folders were like directory folders. But imap doesn't have anything like 'chdir somedir; ls;' which would make it sensible to treat dbmail's mailboxes as nodes in a tree.
3) Add an OrdinalValue field (this is mostly for web-front ends) but it would allow certain mailboxes to be "forced" into a position like Inbox being listed first, Sent-Mail second, etc.
Ahem. Most imap clients don't have any trouble understanding the need to present the special mailboxes before the rest.
4) Path would be a list of ID's with slashes like /1/3/5 where one is the main parent, 3 is a child and 5 is the next child in line.
The brilliant reasoning here escapes me completely :-)
I realize the second 2 are reaches but I figured I would try anyway.
Well, assuming you're working on a web frontend these changes somehow strike me as coming from a certain 'laziness' on your part, if you pardon my french. Just add any fields you need, as you like. Or add an additional table that holds them. If you're using postgres you could probably even use triggers to fill most of them. If not you'd have to write your code to update those fields as required.
-- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
