Congratulations and thanks to all concerned in getting the SQL/MED / Foreign Data Wrapper feature done. Now it's committed, I'm going to build a few. I have a couple of ideas, but I'm also trying to come up with useful but possibly a bit more way out things to wrap. Twitter has already been suggested as a data source, so I'm trying to thing of similarly slightly wacky ideas
Now, if we had DDL triggers we could tie it to this Github API and get integrated database versioning <img src="/andrew/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" />
Reaaly?! I didn't know that; I haven't been following -hackers too closely.<br />
Even so, if can we have RULEs on FDW tables (not sure if we can) we can call functions as part of INSTEAD OF INSERT that make appropriate HTTP API call to Github.
Does it already support XML. Those are the type of feeds I need to contend with. Usually nothing fancy but pretty much like the output you get form query_to_xml. <br />
Also JSON would be nice since I have a couple of services that spit that out and would be nice to consume directly.
It can be wrong expectation <img src="/andrew/templates/default/img/emoticons/smile.png" alt=":-)" style="display: inline; vertical-align: bottom;" class="emoticon" /> - when everybody expects so somebody will do same work and nobody does it in reality.
How about writing some great documentation about how to implement an SQL/MED wrapper, with an example project to read something relatively simple?<br />
That way it would help get more of us implementing many more wrappers...