We should ensure indexing works well with extremely large number of email messages. I had to disable Thunderbird's index database (they use SQL Lite3 - I think) because every time I received a new email, TB would stop for 1/2 - 1 while it managed the index database.

Hey Dan,

As I was preparing to strip the search-arguments I noticed many repeated SQL calls within the thread_id's (each independent SQL connection).

Optional Parent FK's

Ah, so do we want to do this as it gives each [ResourceTable] row the option to create its own [CollectionAttributeTypeTable] rows.

I'm not sure what you mean by "does each [ResourceTable] get its own" - there's only one [ResourceTable] - if you are asking if each Resource in the [ResourceTable] gets it's own "domain" then no, all Resources share the same table space.

Assuming you only lose your database, just creating a new database

We can normalize the [CollectionAttributeTable].type column by moving the key names to their own table like we do in [PartTable] as suggested in the link, but that's about all that I could find there that would apply in our case.

Hey Daniel, I like the idea of having a GUI to allow users to tweak the DBMS settings!

Flags should be NOT NULL

Hi Sandro,

I have attached the latest ERD's. These are printer-friendly (no color). I had to jig the ERD tool's XML file for MySQL.

I've spot-checked the ERD's and they appear to be correct based on the provided SQL. In fact, I pointed the ERD tool to my Neon VM and told it to reverse engineer the run-time akonadi database.

A good way to easily share the MySQL local Instance.

Whaddya know! :) .. however the ERD in the documentation doesn't quite match the table names. I suppose it's like a Logical Model