DB BUG: event id column is redundant
Bug #488550 reported by
Seif Lotfy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zeitgeist Framework |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
we currently have the id in event set but if u notice it always matches the "rowid" since we just increment.
This should be fixed and it will save us one index :) "rowid" is indexed by default
Revision history for this message
| Seif Lotfy (seif) wrote | #1 |
Revision history for this message
| Mikkel Kamstrup Erlandsen (kamstrup) wrote | #2 |
| Changed in zeitgeist: | |
| status: | New → Invalid |
To post a comment you must log in.
This is a coindidental match. The event.id column is not a primary key (as rowid is). We can have multiple subjects/event which will give more than one row with the same event id.