Re: Guidance needed on an alternative take on common prefix SQL

2019-08-07 Thread Rob Sargent
On 8/7/19 3:36 AM, Laura Smith wrote: On Wednesday, August 7, 2019 2:01 AM, Andy Colson wrote: On 8/6/19 6:25 PM, Laura Smith wrote: Hi, I've seen various Postgres examples here and elsewhere that deal with the old common-prefix problem (i.e. "given 1234 show me the longest match"). I'm i

Re: Guidance needed on an alternative take on common prefix SQL

2019-08-07 Thread Laura Smith
On Wednesday, August 7, 2019 2:01 AM, Andy Colson wrote: > On 8/6/19 6:25 PM, Laura Smith wrote: > > > Hi, > > I've seen various Postgres examples here and elsewhere that deal with the > > old common-prefix problem (i.e. "given 1234 show me the longest match"). > > I'm in need of a bit of guid

Re: Guidance needed on an alternative take on common prefix SQL

2019-08-06 Thread Andy Colson
On 8/6/19 6:25 PM, Laura Smith wrote: Hi, I've seen various Postgres examples here and elsewhere that deal with the old common-prefix problem (i.e. "given 1234 show me the longest match"). I'm in need of a bit of guidance on how best to implement an alternative take. Frankly I don't quite kn

Guidance needed on an alternative take on common prefix SQL

2019-08-06 Thread Laura Smith
Hi, I've seen various Postgres examples here and elsewhere that deal with the old common-prefix problem (i.e. "given 1234 show me the longest match"). I'm in need of a bit of guidance on how best to implement an alternative take. Frankly I don't quite know where to start but I'm guessing it wi