Navigation Menu

Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #4367] workaround on libdbi fetch_next_row() bug applied for postgresql too, causing faulty queries #1299

Closed
icinga-migration opened this issue Jul 1, 2013 · 4 comments
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/4367

Created by mfriedrich on 2013-07-01 20:48:49 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2013-07-07 18:58:41 +00:00)
Target Version: 1.9.3
Last Update: 2014-12-08 14:38:10 +00:00 (in Redmine)

Icinga Version: 1.10.0
OS Version: any

the offset, stride limit syntax is mysql only and causes errors on postgresql.

Jul  1 22:34:43 sol ido2db: Error: database query failed for 'SELECT object_id, objecttype_id, name1, name2 FROM icinga_objects WHERE instance_id=1 LIMIT 49605000, 2500' - 'ERROR:  LIMIT #,# syntax is not supported#012LINE 1: ...e1, name2 FROM icinga_objects WHERE instance_id=1 LIMIT 4960...#012 

correct would be: LIMIT x OFFSET y instead of LIMIT y,x

Changesets

2013-07-01 20:47:35 +00:00 by (unknown) 09398fd

idoutils: fix postgresql limit x,y -> limit y offset x

refs #4367

2013-07-01 20:50:25 +00:00 by (unknown) fc56956

idoutils: fix postgresql limit x,y -> limit y offset x

refs #4367

2013-07-07 15:47:36 +00:00 by (unknown) cbcffe6

fix workaround on libdbi fetch_next_row() bug applied for postgresql too, causing faulty queries

fixes #4367
@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-07-07 15:36:19 +00:00

  • Subject changed from postgresql wrong limit select to workaround on libdbi fetch_next_row() bug applied for postgresql too, causing faulty queries
  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-07-07 15:37:03 +00:00

  • Target Version set to 1.9.3

@icinga-migration
Copy link
Author

Updated by Anonymous on 2013-07-07 18:58:41 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset icinga-core:cbcffe6e171d0e79beb453cbdbf533aa263e8a38.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-12-08 14:38:10 +00:00

  • Project changed from 18 to Core, Classic UI, IDOUtils
  • Category changed from 57 to IDOUtils
  • Icinga Version changed from 1 to 1
  • OS Version set to any

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant