#9344 closed defect (wontfix)
sqlite db lack of primary keys
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | database backend | Version: | |
| Severity: | critical | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I create my trac enviromnets using a sqlite database, it works very well.
Now i want to get some information directly from the database the problem is that some tables are create without primary keys and i need them.
I believe the problem is in sqlite_backend.py but python isn't my speciality and i'm in a hurry so if you can guide me to a quick fix. thank you.
Attachments (0)
Change History (4)
follow-up: 2 comment:1 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
follow-up: 3 comment:2 by , 16 years ago
Replying to cboos:
As you're in a hurry, I'll make it short: asking us to change our datamodel, adding primary keys just because "you need them" sounds like a joke. Please be serious, if you are able to articulate why you need them, convince us it's a valuable change, provide a patch, etc. then this might be considered, otherwise it's just non-sense.
i'm not saying to change your datamodel, sorry if i not explain things clearly.
In http://trac.edgewall.org/wiki/TracDev/DatabaseSchema the tables attachment, auth_cookie, enum, node_change, permission, session, session_attribute, ticket_change, ticket_custom are defined with primary keys.
when i browse the file trac.db (default) the tables aren't defined with the primary_keys specified in the schema.
Sorry to bother you. I will try to solve the problem my self, only came here cause iḿ not familiar with the structure and the language and i considered this problem as a bug,
Have a nice day!
comment:3 by , 16 years ago
Replying to anonymous:
Replying to cboos:
As you're in a hurry, I'll make it short: asking us to change our datamodel, adding primary keys just because "you need them" sounds like a joke. Please be serious, if you are able to articulate why you need them, convince us it's a valuable change, provide a patch, etc. then this might be considered, otherwise it's just non-sense.
i'm not saying to change your datamodel, sorry if i not explain things clearly.
In http://trac.edgewall.org/wiki/TracDev/DatabaseSchema the tables attachment, auth_cookie, enum, node_change, permission, session, session_attribute, ticket_change, ticket_custom are defined with primary keys.
I see … but this page is not a specification of what "should be", rather an a posteriori attempt to document what "is".
when i browse the file trac.db (default) the tables aren't defined with the primary_keys specified in the schema.
Sorry to bother you. I will try to solve the problem my self, only came here cause iḿ not familiar with the structure and the language and i considered this problem as a bug,
Ok, no harm done ;-) But it's not a bug, at most a deficiency in the documentation, which you're welcome to improve.
comment:4 by , 16 years ago
I solved the problem where can i make the change or what can i do ?!
Sorry if not the right place =(
As you're in a hurry, I'll make it short: asking us to change our datamodel, adding primary keys just because "you need them" sounds like a joke. Please be serious, if you are able to articulate why you need them, convince us it's a valuable change, provide a patch, etc. then this might be considered, otherwise it's just non-sense.