Timeline for Working with JSON data MySQL
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2017 at 9:41 | comment | added | til_b | Yes, but the conclusion seems that it is not a bug, but the wrong usage of the wildcard search. | |
| Jan 18, 2017 at 22:23 | comment | added | Anthony S. | I wasn't crazy! I don't know if you guys actually reviewed/tested,but apparently Oracle has reproduced this. bugs.mysql.com/bug.php?id=84523 | |
| Jan 17, 2017 at 14:38 | comment | added | Anthony S. | The problem here is that the array format shown in the documentation does not work - the original [ { "key" : { "key" : "value" } } ] format I was using. Querying based on '$.Key' returns null, and querying based on '$**.Key' takes 30 seconds with a 1 row constraint. By putting it into the non-proper format, I can then properly query on '$.Key', instantly. | |
| Jan 17, 2017 at 5:28 | comment | added | The Coder |
{"key":{"subkey":"val","subkey":"val"}}, {"key":{"subkey":"val","subkey":"val"}} is not a valid array. You should first refer the official documentation dev.mysql.com/doc/refman/5.7/en/json.html
|
|
| Jan 16, 2017 at 19:19 | history | answered | Anthony S. | CC BY-SA 3.0 |