| Summary | VFS Folder creation broken |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 3. High |
| Owners | slusarz (at) horde (dot) org |
| Requester | slusarz (at) horde (dot) org |
| Created | 03/24/2011 (5242 days ago) |
| Due | |
| Updated | 03/24/2011 (5242 days ago) |
| Assigned | 03/24/2011 (5242 days ago) |
| Resolved | 03/24/2011 (5242 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | 4 |
| Patch | No |
Assigned to Michael Slusarz
Summary ⇒ VFS Folder creation broken
State ⇒ Resolved
Bug #9711: Fix VFS SQL callThis was breaking autoincrement on postgresql
2 files changed, 11 insertions(+), 9 deletions(-)
http://git.horde.org/horde-git/-/commit/0e996549bd41236f76e7f9bd8aa6a936d7de703b
Revert "
Bug #9711: Fix creation of auto-increment columns in Postgresql"This reverts commit 395a6e1f5eaf894889892e2d1c58f5bb71a22188.
Problem occurred in VFS library. Added more complete unit tests.
3 files changed, 40 insertions(+), 13 deletions(-)
http://git.horde.org/horde-git/-/commit/07c40864adc4f8f8d05a95ba75321d09daef7e4c
State ⇒ Feedback
autoincrementing work). I just don't know if these are correct
assumptions for primaryKey.
Two further thoughts:
1. According to the 'primaryKey' implementation in the Postgresql
schema class, primaryKey is expected/required to be an autoincrement
column. If that is the case, we should really pick a different name
(e.g. 'autoincrementKey') since non-autoincrement columns can also be
primary keys.
2. 'primaryKey' (or 'autoincrementKey' or whatever) should be a
defined constant.
Bug #9711: Fix creation of auto-increment columns in Postgresql2 files changed, 12 insertions(+), 8 deletions(-)
http://git.horde.org/horde-git/-/commit/395a6e1f5eaf894889892e2d1c58f5bb71a22188
Taken from
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Postgresql autoincrement broken
Queue ⇒ Horde Framework Packages
Assigned to
Milestone ⇒ 4
Patch ⇒ No
State ⇒ Assigned
contains a not-null constraint.