Talk:Extension Manager:Sqlite Storage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
The main Add-ons manager UI has to cope with the same problem, it will use sqlite templates. I don't see a reason why Seamonkey wouldn't be able to use the same. | The main Add-ons manager UI has to cope with the same problem, it will use sqlite templates. I don't see a reason why Seamonkey wouldn't be able to use the same. | ||
: [[User:Mossop|Mossop]] | : [[User:Mossop|Mossop]] | ||
''Rather than being customised for displaying appropriately in the UI the database should instead be properly normalised with whatever information we need now and may need in the future. It should not include transient data that is only needed before the app restarts to keep the UI correct.'' | |||
It isn't clear to me how database normalization applies to customised for displaying appropriately in the UI. | |||
--[[User:Robert Strong|Robert Strong]] 12:54, 10 July 2008 (PDT) | |||
Revision as of 19:54, 10 July 2008
So how will that affect this?
The main Add-ons manager UI has to cope with the same problem, it will use sqlite templates. I don't see a reason why Seamonkey wouldn't be able to use the same.
Rather than being customised for displaying appropriately in the UI the database should instead be properly normalised with whatever information we need now and may need in the future. It should not include transient data that is only needed before the app restarts to keep the UI correct.
It isn't clear to me how database normalization applies to customised for displaying appropriately in the UI. --Robert Strong 12:54, 10 July 2008 (PDT)