Jira (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Change By: Morgan Rhodes Sprint: Release Engineering Hopper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.107195.1448476899000.163887.1615490820434%40Atlassian.JIRA.
Jira (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Change By: Zachary Kent Sprint: Release Engineering Hopper Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.107195.1448476899000.162689.1615408440885%40Atlassian.JIRA.
Jira (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Change By: Zachary Kent Sprint: Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.107195.1448476899000.162650.1615408381063%40Atlassian.JIRA.
Jira (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Change By: Rob Browning Sprint: Data Platform 2018-05-23 Hopper/Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Issue Type: Improvement Assignee: Unassigned Created: 2015/11/25 10:41 AM Priority: Normal Reporter: Wyatt Alt We currently use _expression_ indexes on our uuid/hash columns to make queries fast, because we realized shortly before 3.2.2 that we were issuing queries against columns cast to text, which prevented the indexes from being used. _expression_ indexes were a quick fix without much migration overhead, but long term we should get this buttoned down so that we're using consistent types internally (preferably bytea/uuid, but varchar works too). This probably means either extending clojure.jdbc to do the type coercion on result sets, or adding some munging in the query namespaces to handle the byte arrays there. Add Comment
