#8 separate dbmail and webdbmail databases


In a future version I really like to see a separate
database for webdbmail to store it's features, away
from dbmail.

I don't like the idea that my dbmail tables have
changed. There is no way of knowing what that does to
dbmail's stability.

so, webdbmail should be able to access 2 databases.


  • Logged In: YES

    the stability of my dbmail server is everything!

    with that respect a webmail client is only a small feature..

    • priority: 5 --> 1
  • Logged In: YES

    I can understand the hesitancy where you may not know what
    it does to dbmail's stability - however, some of the
    features (such as Starring, and the Trash Can) are better
    kept in the messages table.

    Another thing about multiple databases is that it would
    require two connections (one for each db) for operation
    which is more CPU intensive than one.

    So far I have not seen any stability problems in regards to
    dbmail (doesn't mean there isn't any).

    I will keep this feature in mind, but I don't think I'll do
    anything until not doing causes a verifiable problem.

  • Logged In: YES

    Final on this - as suggested by a dbmail developer.

    No changes will be made to the original dbmail tables.

    To keep things separate custom data will be stored in
    dbwebmail_ tables to avoid any namespace issues (maintenance

    The installer is being modified now, and shortly following
    the rest of dbWebmail will be updated as well.

    • priority: 1 --> 7
    • assigned_to: nobody --> borvik
    • status: open --> pending
    • priority: 7 --> 1
    • status: pending --> closed
  • Logged In: YES

    Completed transition over to new database structure.