News for hackers. Stuff that matters.
Re:MySQL 8.0 Labs: JSON aggregation functions by greenlet on Thursday October 06, 2016 @04:29PM (#12655836)
how does mysql's json type compare to postgres' jsonb? my biggest gripe with both of them is lack of partial update
Re:MySQL 8.0 Labs: JSON aggregation functions by morgo on Thursday October 06, 2016 @04:52PM (#12656007)
No partial update yet, but we are working towards it -

The json binary format spec allows for padding. Search in page for 'BLOB' for details: http://mysqlserverteam.com/the-mysql-8-0-0-milestone-release...

Re:MySQL 8.0 Labs: JSON aggregation functions by Psyonic on Thursday October 06, 2016 @04:44PM (#12655939)
jsonb_set is available now in postgres 9.5: https://www.postgresql.org/docs/9.5/static/functions-json.ht...
Re:MySQL 8.0 Labs: JSON aggregation functions by th3sly on Thursday October 06, 2016 @04:48PM (#12655963)
but that's not partial update. this will update the entire document(blob).
Re:MySQL 8.0 Labs: JSON aggregation functions by semiquaver on Thursday October 06, 2016 @05:31PM (#12656286)
Postgres' MVCC architecture makes the idea of 'partial updates' kind of meaningless. An update to any postgres column is equivalent to a DELETE followed by an INSERT and will result in a new row on disk, leaving the old row to be vacuumed later.
Re:MySQL 8.0 Labs: JSON aggregation functions by morgo on Thursday October 06, 2016 @05:48PM (#12656407)
Just to clarify: s/architecture/implementation/

InnoDB is MVCC too, but does an update in place with relocation of the old row to UNDO space. There are pros and cons to both approaches.