-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #8613] IDO queries related to concrete objects should not depend on collations #1429
Comments
Updated by tgelf on 2015-03-05 15:02:16 +00:00
|
Updated by elippmann on 2015-03-05 15:40:48 +00:00
|
Updated by tgelf on 2015-03-05 15:42:44 +00:00
If I correctly remember what we discussed a while ago one way of solving this could be to remove collations from host_name, service_description, service_host_name and similar and keep host, service and eventually host_service as their respective collate'd aliases. What do you think about this? Cheers, |
Updated by jmeyer on 2015-04-08 08:11:47 +00:00
|
Updated by jmeyer on 2015-04-08 08:30:30 +00:00
|
Updated by jmeyer on 2015-04-09 08:47:26 +00:00
|
Updated by elippmann on 2015-04-10 08:25:53 +00:00
|
Updated by icinga-kanban on 2015-04-10 17:03:53 +00:00 Build !#585 triggered by the commits c10617d, c59d5ac, e7c1e55, ea16d45, 42e93ff, 8b2c019, 904e91b, 629becf, 4bc3afa, fdd6a4d, 055cd61, a17c2ed, 26f0b46, f61370f, 69e520a, 9f075e0, 1f4b3aa, 92634a1, 5ccf6a7, 0f07274, 1c32d8e, fda261b, b8efe01, 0628efb, 638eda7, 0fe59aa, 03c8de5, 31a05a3, a51b93e, 5ec4919, 71c0131, 6536878, 1dc16a1, 8477859, 3d7e418, 6d03b2f, 0ec1a18, 52dcecf, f00adc2, 3c47ba1 passed successfully. Branch: origin/feature/non-collated-ido-queries-8613 |
Updated by jmeyer on 2015-04-13 13:56:55 +00:00
Applied in changeset 46296dc. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8613
Created by tgelf on 2015-03-05 15:02:06 +00:00
Assignee: jmeyer
Status: Resolved (closed on 2015-04-13 13:56:55 +00:00)
Target Version: 2.0.0-rc1
Last Update: 2015-04-13 13:56:55 +00:00 (in Redmine)
We use COLLATE as we need to issue case insensitive search queries. For MySQL they look as follows:
While this perfectly makes sense when searching, it absolutely doesn't when we alreay know the exact object name. In theory we could base queries on IDs for IDO backends. We don't, as we want all our backends to behave as similar as possible, offering the very same abstraction level.
It's however perfectly valid to use those COLLATE-based columns for search only. This will boost our detail area and all queries issueing a complicated joins.
Best,
Thomas
Changesets
2015-03-12 15:32:05 +00:00 by elippmann 7212434
2015-03-12 15:33:28 +00:00 by elippmann 112f8eb
2015-04-08 12:40:34 +00:00 by jmeyer b449127
2015-04-08 12:41:13 +00:00 by jmeyer 98c76a6
2015-04-08 12:42:57 +00:00 by jmeyer c476ee6
2015-04-08 12:49:18 +00:00 by jmeyer 9557585
2015-04-08 12:51:04 +00:00 by jmeyer c56c565
2015-04-08 12:57:08 +00:00 by jmeyer e94c99e
2015-04-08 12:57:30 +00:00 by jmeyer 55e9407
2015-04-08 14:25:29 +00:00 by jmeyer b93d18a
2015-04-08 14:49:52 +00:00 by jmeyer 09ab601
2015-04-09 08:27:41 +00:00 by jmeyer b9aee47
2015-04-09 08:28:34 +00:00 by jmeyer cee189a
2015-04-09 09:12:09 +00:00 by jmeyer 7d98466
2015-04-09 09:41:56 +00:00 by jmeyer f7550f5
2015-04-09 09:43:21 +00:00 by jmeyer e5eca97
2015-04-09 09:43:51 +00:00 by jmeyer 1e6f292
2015-04-09 10:49:06 +00:00 by jmeyer cb95f53
2015-04-09 10:53:28 +00:00 by jmeyer 480f551
2015-04-09 10:55:57 +00:00 by jmeyer 002b820
2015-04-09 10:56:31 +00:00 by jmeyer 8ed1c8e
2015-04-09 11:06:38 +00:00 by jmeyer 21c7601
2015-04-09 11:07:50 +00:00 by jmeyer 5372dfb
2015-04-09 12:17:27 +00:00 by jmeyer 84a2727
2015-04-09 12:19:31 +00:00 by jmeyer 2c38ccd
2015-04-09 12:39:47 +00:00 by jmeyer ae10e01
2015-04-09 12:40:12 +00:00 by jmeyer b7e1c2d
2015-04-09 12:41:10 +00:00 by jmeyer ec67c28
2015-04-09 12:44:10 +00:00 by jmeyer 9e79419
2015-04-09 13:13:59 +00:00 by jmeyer 51bf5cf
2015-04-09 13:29:01 +00:00 by jmeyer ea874f8
2015-04-10 07:39:39 +00:00 by jmeyer 3c47ba1
2015-04-10 07:45:23 +00:00 by jmeyer f00adc2
2015-04-10 07:46:41 +00:00 by jmeyer 52dcecf
2015-04-10 07:48:22 +00:00 by jmeyer 0ec1a18
2015-04-10 07:49:47 +00:00 by jmeyer 6d03b2f
2015-04-10 07:50:26 +00:00 by jmeyer 3d7e418
2015-04-10 10:12:50 +00:00 by jmeyer 1dc16a1
2015-04-10 10:13:23 +00:00 by jmeyer 6536878
2015-04-10 10:14:11 +00:00 by jmeyer 71c0131
2015-04-10 10:14:47 +00:00 by jmeyer 5ec4919
2015-04-10 10:20:28 +00:00 by jmeyer 03c8de5
2015-04-10 10:27:24 +00:00 by jmeyer 638eda7
2015-04-10 10:27:44 +00:00 by jmeyer 0628efb
2015-04-10 10:56:18 +00:00 by jmeyer b8efe01
2015-04-10 12:19:38 +00:00 by jmeyer fda261b
2015-04-10 12:23:05 +00:00 by jmeyer 1c32d8e
2015-04-10 12:24:53 +00:00 by jmeyer 0f07274
2015-04-10 12:25:26 +00:00 by jmeyer 5ccf6a7
2015-04-10 12:25:53 +00:00 by jmeyer 92634a1
2015-04-10 13:04:59 +00:00 by jmeyer 1f4b3aa
2015-04-10 13:19:55 +00:00 by jmeyer 9f075e0
2015-04-10 13:20:19 +00:00 by jmeyer 69e520a
2015-04-10 13:21:18 +00:00 by jmeyer f61370f
2015-04-10 13:31:09 +00:00 by jmeyer 26f0b46
2015-04-10 13:31:51 +00:00 by jmeyer a17c2ed
2015-04-10 13:32:47 +00:00 by jmeyer 055cd61
2015-04-10 13:34:28 +00:00 by jmeyer fdd6a4d
2015-04-10 13:34:55 +00:00 by jmeyer 4bc3afa
2015-04-10 13:35:24 +00:00 by jmeyer 629becf
2015-04-10 13:54:18 +00:00 by jmeyer 904e91b
2015-04-10 13:54:55 +00:00 by jmeyer 8b2c019
2015-04-10 13:58:55 +00:00 by jmeyer 42e93ff
2015-04-10 14:01:09 +00:00 by jmeyer ea16d45
2015-04-10 14:01:22 +00:00 by jmeyer e7c1e55
2015-04-10 14:28:33 +00:00 by jmeyer c59d5ac
2015-04-10 14:28:57 +00:00 by jmeyer c10617d
2015-04-13 13:24:15 +00:00 by jmeyer 96954ea
2015-04-13 13:25:10 +00:00 by jmeyer 15399d7
2015-04-13 13:26:06 +00:00 by jmeyer 644a386
2015-04-13 13:32:52 +00:00 by jmeyer 3653ec8
2015-04-13 13:33:19 +00:00 by jmeyer 29f05bf
2015-04-13 13:33:33 +00:00 by jmeyer 9cc5469
2015-04-13 13:55:53 +00:00 by jmeyer 46296dc
Relations:
The text was updated successfully, but these errors were encountered: