I admit I was very aware of the "(preview)" suffix on the database connection link in the portal and documentation.
It's very disappointing that there's so little support. It's all well and good saying 'host your own instance' and there is guidance to do that, there is no guidance, that I have found, that can walk me through hosting it for dev purposes and updating the deployment pipelines.
I tried implementing all the data-api endpoints explicitly in the Azure Function but the output sql bindings that insert a record don't return anything, so there's no way of returning a new records primary key. I tried stored procs but they don't seem to work with output bindings either.
Not really an answer but as far as I can tell the options are:
- follow their guidance and deploy DAB and work out how that manifests in dev and deployment or
- add explicit endpoints to your azure function for all the queries / crud operations and add some correlationid to each of my tables so I can query for records once they've been inserted.