If you are referring to cross database queries using that syntax wouldn't that require reworking the transaction system to work across db's to guarantee ACIDity?
On Sun, Jul 21, 2019 at 10:24 AM jmz <mxav1111@xxxxxxxxx> wrote:
Thank you for the clarification David. I really thought this would be easier to implement since rest of the architecture (within DB) doesn't need any (or little) change.Max.On Sat, Jul 20, 2019, 19:35 David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:On Saturday, July 20, 2019, jmz <mxav1111@xxxxxxxxx> wrote:Does any one know if database.schema.table syntax would make it to Release 12?No. The lack of an entry in the beta release notes (or relevant documentation) and probably the same error when attempting it on version 12 makes this clear.There is no pending patch or even, IIRC, recent discussion on making this potentially a thing. My understanding is the current architecture of the product makes implementing such a capability prohibitively expensive in terms of both time and risk.David J.
