Re:Chartio develops non-blocking MySQL queries using Tornado
by gaius on Friday June 10, 2011 @05:26PM
(#2642474)
Interesting, Oracle is currently recommending not using async OCI calls in the 11g documentation (altho' the feature is obviously there), instead they recommend you to use blocking calls on separate threads. This means you can get notified when your query completes on the client with no network roundtrip to find out if it's still executing.
[ Parent
| on HN ]
Re:Chartio develops non-blocking MySQL queries using Tornado
by kevingadd on Friday June 10, 2011 @10:30PM
(#2643061)
There's no reason completion notifications can't occur in an async API. It sounds like oracle calls polling "asynchronous", which is not particularly accurate. If the polling operations also involve network round trips to check for query completion, that is a tremendously stupid API.
Re:Chartio develops non-blocking MySQL queries using Tornado
by gaius on Saturday June 11, 2011 @03:38AM
(#2643420)
Reason's simple: you have to support in your 11g server clients written in the dim and distant past, so you can't monkey with the protocol too much. You could do this as you suggest by subscribing for DCN events when your transaction completes, but obviously not with SELECTs.
Re:Chartio develops non-blocking MySQL queries using Tornado
by jacques_chester on Saturday June 11, 2011 @03:12AM
(#2643392)
Oracle is a funny beast. Like other gold-tooth-money databases it has some amazingly advanced features. But in other ways it is more 1980s than Top Gun crossed with Duran Duran.
It still doesn't have a native boolean type in SQL, for example. After 30 years.