Tickets :: [#12361] rampage_tag_stats has primary key tag_id with no default sequence

6.0.0-RC7

6/28/26

History
Attachments
Comment
Watch
Download

Summary	rampage_tag_stats has primary key tag_id with no default sequence
Queue	Content
Queue Version	2.0.2
Type	Bug
State	No Feedback
Priority	1. Low
Owners
Requester	michael (at) bigmichi1 (dot) de
Created	6/16/13 (4760 days ago)
Due
Updated	1/20/14 (4542 days ago)
Assigned	6/18/13 (4758 days ago)
Resolved	10/9/13 (4645 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

212	amessina (at) messinet (dot) com	Comment #4	Reply to this comment
I can confirm this issue as reported using Horde 5.1.5 and Ansel 3.0.1 with a PostgreSQL backend.

542	Jan Schneider	State ⇒ No Feedback

3812	Jan Schneider	Comment #3	Reply to this comment
I don't see this running the unit tests of Content on Postgres.

52	Michael Rubinsky	Comment #2 State ⇒ Feedback	Reply to this comment
This is coming from Horde_Db. It looks like it assumes that any primary key should be an autoincrement sequence when using psql. See e.g., Horde_Db_Adapter_Pdo_Pgsql::insert. I don't think this is the correct behavior. At the very least, if it's not possible to know if we have a sequence when we call these methods, we shouldn't output the warning, as it's expected behavior in this case.

4411	Jan Schneider	Queue ⇒ Content Version ⇒ 2.0.2

3111	michael (at) bigmichi1 (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ rampage_tag_stats has primary key tag_id with no default sequence Queue ⇒ Kronolith Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
when i'm using kronolith the following messages pops up in my horde log file: 2013-06-16T09:17:01+02:00 WARN: HORDE [kronolith] rampage_tag_stats has primary key tag_id with no default sequence [pid 4456] I'm using a fresh horde5 installation with postgresql backend