As usual you are way ahead of me. I was just thinking about returning result rows - a la JDBC - wrapped in JSON. And apparently I was not thinking all that clearly.
Your observation about character-only data might be enough to put this idea (not originally mine) to rest. On Jul 31, 2014, at 5:43 PM, Jim Starkey wrote: > First, rest isn't remotely feasible for a SQL protocol. SQL requires > state to be maintained from call to call, especially to do atomic > transactions. > > It is possible to build a richer command language to encapsulate > multiple updates, multiple retrievals, exception handling and reporting, > etc. The AmorphousDB interface is designed to do this, but it isn't > SQL. By the time you've extended SQL to handle everything necessary, it > doesn't look or behave like SQL any more. > > And then there is the nasty problem that JSON only handles character > data. Do you really want to turn binary blobs into base-64 for the line > protocol? ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
