cancel
Showing results for 
Search instead for 
Did you mean: 

Webinar: JSON and JSONPATH in Postgres 12

Community Manager

Webinar: JSON and JSONPATH in Postgres 12

 

The Pulse of Postgres Slim.png

 

Coming Soon: JSON and JSONPATH in Postgres 12

With Marc Linster and Thom Brown

 

Date: October 23rd, 2019
Time: 10.00am ET | 16.00 CET | 15.00 GMT

 

Join Postgres experts, Marc Linster and Thom Brown, as they discuss jsquery. Jsquery was introduced to allow more sophisticated querying of JSON data with indexing support. However, this was an external project, with no official support. SQL/JSON is now coming in Postgres 12 which will provide very similar functionality. This webinar will compare jsquery and SQL/JSON by discussing:

  • The similarities and differences between the two features
  • The equivalent functionality where they aren't identical
  • Examples of how they compare in practice
About the Speakers: 
Marc Linster, SVP, Product Development & Support
Thom Brown, Engineering Project Manager
 
 
Register Now Marketo.png
1 REPLY 1
Highlighted
Community Manager

Re: Webinar: JSON and JSONPATH in Postgres 12

Follow Up: [WEBINAR]  JSON and JSONPATH in Postgres 12

 

We hope you had a chance to join us for the webinar!!   If not, don't worry! 

You can view the webinar via the link below. Be sure to check out the Q & A Session too!

 

VIEW THE WEBINAR:  JSON and JSONPATH in Postgres 12

 

Q & A SESSION:

__________________

 

Question:

Generally speaking, when is a JSONB data type appropriate and when would you advise using traditional SQL data types?  Is there a significant performance difference when searching large tables? 

 

Answer:

JSONB format is great when you need the flexibility, for example, if you don’t know how many phone numbers a contact will have and how they will be labeled (mobile, home, weekend, camper, …).

Query performance is comparable, but update performance needs to be monitored, as an update will always rewrite the whole JSONB document.

_____

 

Question:

Can you please explain the difference between SQL NULL and jsonpath NULL?

 

Answer:

A null value in JSON represents a blank value and can be directly compared to other JSON null values using equality and inequality operators. An SQL NULL value represents an unknown value. So with a JSON null we know the value, but with an SQL NULL, the value is absent so we can't say whether it is equal to any other SQL NULL.

_____

 

Question:

How the updates will happen to update multiple attributes in a jsonb doc?

 

Answer:

Updates always rewrite the whole JSONB document.

_____