<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, May 19, 2015 at 10:31 PM, Greg Sabino
Mullane<span dir="ltr"><<a href="mailto:greg@turnstep.com" target="_blank">greg@turnstep.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><spanclass=""><br /></span>If you are running into situations<br /> where you have
questionmark operators in your queries, you have already lost<br /> the query abstraction battle. There will be no
seamlessswitching if you<br /> are using jsonb, hstore, ltree, etc.<br /></blockquote></div><br /></div><div
class="gmail_extra">Actually,no, you haven't quite lost that battle, or rather, that battle doesn't even need to take
place.<br/><br /></div><div class="gmail_extra">You can still use common tools for operations that are not really
RDMBS-specificAND use PostgreSQL extensions on a case-by-case basis depending on your application requirements.<br
/></div><divclass="gmail_extra">Some of these tools already allow you to tweak slightly their capabilities by
implementingdialects, and let you use specific features if required.<br /><br />I think this is a major advantage of
havingthese extensions in PostgreSQL: you can have the best of both worlds. It's not so much about being able to switch
toanother RDMBS, it's about not having to re-implement the bulk of the structure when you just want to benefit from a
fewadditional extensions (for example, mixing the classic RDBMS model with the JSON store model).<br /></div><div
class="gmail_extra"><br/></div><div class="gmail_extra">Best wishes,<br /><br /></div><div
class="gmail_extra">Bruno.<br/></div><div class="gmail_extra"><br /><br /></div></div>