Ihar Hrachyshka wrote:
> That’s an interesting precedent. I understand that since we gate on
> postgresql and mysql only, the solution is good enough to pass in the gate.
> But are we ok fixing a bug just for those two backends, knowing that it’s
> left exposed for other backends? Could you think of a solution that would be
> backend agnostic?


This is why during the review phase, I objected to using a stored
procedure for this logic, since it is tied very tightly to the database
implementation. 

I also have a lot of scars and recurring nightmares
about an old job where the majority of an application's logic was
embedded in huge stored procedures and database triggers - so I'm a bit
biased.

-- 
Sean M. Collins

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to