We saved $50k/year with a Go microservice coded in a hackathon

Re:We saved $50k/year with a Go microservice coded in a hack... by TimJYoung on Tuesday April 10, 2018 @10:45PM (#16807641)

There's no need for the extra joins, you can just do the one join and then filter everything in the WHERE clause:

  SELECT DISTINCT loyaltyMemberID
  from members as m
  INNER JOIN properties as p on m.id=p.user_id
  WHERE (p.prop='name' AND p.value = value) AND

  ...etc.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by 83457 on Wednesday April 11, 2018 @09:29AM (#16810859)

But how would you do exclusions with your approach?

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by TimJYoung on Thursday April 12, 2018 @05:11AM (#16819177)

I'm not sure what you're asking - could you give me an example of what you're envisioning that couldn't be satisfied with a combination of Boolean expressions in the WHERE clause ?

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by 83457 on Thursday April 19, 2018 @01:51PM (#16878198)

With this query approach how do you find people that have a prop1 but do not a prop2?

If you get records back with prop1 then you have to remove those records from results based on another record.

There are multiple ways to accomplish this but it can't be done with a single join and simple where clause.

[ Parent | on HN ]

Re:We saved $50k/year with a Go microservice coded in a hack... by TimJYoung on Tuesday May 01, 2018 @08:42PM (#16973140)

Sorry, I missed your reply. Yes, you are correct, in that case you would need to use a except, sub-query, derived table, etc.

[ Parent | on HN ]