|
|
Line 399: |
Line 399: |
|
| |
|
| === v2.0 Schema === | | === v2.0 Schema === |
| The [http://oregonstate.edu/~morgamic/umo/umo.png first draft of the v2.0 schema] was drafted at midnight, 05/18.
| | '''v2.0 will be rewritten using the existing data structure.''' Future improvements will be considered as needed. |
|
| |
|
| It was made with [http://www.graphviz.org/ GraphViz]; [http://oregonstate.edu/~morgamic/umo/umo.txt view the source file]. | | For fun, here is the [http://oregonstate.edu/~morgamic/umo/umo.png now-obselete v2.0 db diagram] (05/18). It was made with [http://www.graphviz.org/ GraphViz]; [http://oregonstate.edu/~morgamic/umo/umo.txt view the source file]. |
| | |
| ==== Change Log ====
| |
| * Removed
| |
| ** faq - outsource to wiki, bring back later if needed
| |
| ** feedback_ipbans - user accounts will be required for comment posts, general throttling enabled makes this unnecessary
| |
| :::see my comment above regarding registration for comments --[[User:CTho|CTho]] 19:24, 13 Jun 2005 (PDT)
| |
| ** approvallog - this is replaced by reviews
| |
| ** downloads - this is just deleted, replaced by singular column in addon_versions (throttling, remote limitations pending of course)
| |
| * Added
| |
| ** sessions - track user sessions with more detail, also ensure sess data integrity
| |
| ** app_addon_map - mappings between addon versions and app versions, replacing minver/maxver comps with a simpler query
| |
| ** os_addon_map - mappings between addon versions and operating systems, abstracted to avoid having to hard-code OS id's in UMO application (as in v1.0)
| |
| ** reviews - per-user/per-os review logs, added N times until approval so each item in queue has a running total of "what has been looked at"
| |
| ** comments - replaces feedback, and is now mapped to user_id (login required)
| |
| ** addon_types, addon_type_map - abstracts addon types, so E/T will no longer be hard-coded in UMO application (as in v1.0)
| |
| ** locales, locale_addon_map - per-addon (not per addon version) locale information to help with international extension or theme searches
| |
| | |
| :What if they have one XPI for EN and one XPI for FR? -alanjstr 2005-06-01 14:36 EST
| |
| | |
| :I don't see how you could query for a minver or maxver at all here. There's only one field, not two for min and max. There is not table of app versions. -alanjstr 2005-06-01 14:36 EST
| |
| | |
| *General Changes
| |
| ** naming consistency
| |
| ** better normalization (probably too much, and probably not perfect, but it's a start)
| |
| ** better fits workflow
| |
| | |
| ==== Colin's Comments ====
| |
| | |
| The schema seems reasonable as it stands, although some changes are likely to be necessary pending the discussion above regarding FAQs etc. and whether they should be part of this site, not the Wiki.
| |
| | |
| Other points as follows:
| |
| * It seems comments are per addon version and not per addon? This seems 'wrong' to me.
| |
| * Each addon_version should (perhaps) have a an "approved_time" column, so that the "Newest" Extensions are based on approved time rather than than added time (which could be 5 days earlier)
| |
| | |
| ==== Possible Problems with this draft ====
| |
| * over-normalization
| |
| * lack of download spam checking in DB (still could be mitigated with proper app logic)
| |
| * requiring login for comments might suck, would require a left-join if user_id stays
| |
| * migration will be painful, but it is probably a necessary pain (open for discussion, guys)
| |
|
| |
|
| == Application Structure == | | == Application Structure == |