| Summary | Missing sequence in Ingo's SQL script |
| Queue | Ingo |
| Queue Version | 1.2.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | sebastien-horde (at) orniz (dot) org |
| Created | 07/17/2009 (5958 days ago) |
| Due | |
| Updated | 07/23/2009 (5952 days ago) |
| Assigned | |
| Resolved | 07/17/2009 (5958 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
influence on that.
database user should have the minimal permissions for an application
to work. Here insert/update/delete/select is sufficient...
On the portability point of view, why not provide database specific
scripts and a generic one, Horde already do this...
State ⇒ Not A Bug
Patch ⇒ No
you, then you either have a buggy DB package or your db user doesn't
have permissions to create tables inside the Horde database.
Also, CREATE SEQUENCE is not a portable statement.
Priority ⇒ 2. Medium
New Attachment: ingo-sequence.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ Missing sequence in Ingo's SQL script
Type ⇒ Bug
State ⇒ Unconfirmed
tries to use ingo_rules_seq to generate ID of the new rule, this
sequence isn't created with the provided SQL script.
Attached is a patch that adds this sequence.