6.0.0-git
2019-04-21

[#12361] rampage_tag_stats has primary key tag_id with no default sequence
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 2013-06-16 (2135 days ago)
Due
Updated 2014-01-20 (1917 days ago)
Assigned 2013-06-18 (2133 days ago)
Resolved 2013-10-09 (2020 days ago)
Milestone
Patch No

History
2014-01-20 00:25:02 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.
2013-10-09 14:18:54 Jan Schneider State ⇒ No Feedback
 
2013-08-27 12:34:38 Jan Schneider Comment #3 Reply to this comment
I don't see this running the unit tests of Content on Postgres.
2013-06-18 14:49:05 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.
2013-06-18 11:39:44 Jan Schneider Version ⇒ 2.0.2
Queue ⇒ Content
 
2013-06-16 11:41:31 michael (at) bigmichi1 (dot) de Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Summary ⇒ rampage_tag_stats has primary key tag_id with no default sequence
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
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

Saved Queries