On Wed, Jun 17, 2015 at 4:47 PM, Paul McNett <[email protected]> wrote:
> On 6/17/15 12:43 PM, Stephen Russell wrote: > >> Not sure how many of you work with json. Here is a first write up on >> dealing with it from SQL Server directly, and it is NOT SIMPLE. >> >> http://www.codeproject.com/Articles/1000953/JSON-for-SQL-Server-Part >> > > I work with json every day, and I don't understand this article. You save > json to a field in a table, and use whatever client you want to parse it, > work with it, and then serialize it and save it back. You don't need > special support from the database to serve up json. > ------------ I caught the line that said "Coming in SQL 2016, to do it in current versions.." Thus the API in 2016 will do a lot of that for the user. Otherwise you were just making collections of collections in what they presented. Those C's of C's are what I thought made json unique. -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmyjkmpzqq2vrr3hhc8hznvmwz+lebxslm8na3lg0c-m...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
