Been using json values in databases for a while now and all json functionality added are very well received. That distinct statement, will be verry good. I use a lot of different work around for that particular case. It will be slowly adopted, great.
For the Trim Function we also added keywords Leading Trailing and Both as well as the ability to use the trim functions for character trimming. This should allow for parity if data sets are combined with other sources like Oracle or DB2 data.
So, can I just start using this on my azure SQL databases? Can I assume that these upgrades are pushed automatically to our servers and databases in azure?
Been using json values in databases for a while now and all json functionality added are very well received. That distinct statement, will be verry good. I use a lot of different work around for that particular case. It will be slowly adopted, great.
For the Trim Function we also added keywords Leading Trailing and Both as well as the ability to use the trim functions for character trimming. This should allow for parity if data sets are combined with other sources like Oracle or DB2 data.
So, can I just start using this on my azure SQL databases? Can I assume that these upgrades are pushed automatically to our servers and databases in azure?
404 on the Learn Link
Всем привет . Есть тут люди которые меня понимают ? Зачем вы так себя от людей ограничили языковым барьером ?