Conversation
|
Hello 👋 here is the most recent benchmark result:
This comment gets update everytime a new commit comes in! |
| private static function transformTrace(array $trace): array | ||
| { | ||
| if (array_key_exists('class', $trace) && is_string($trace['class'])) { | ||
| $trace['class'] = str_replace("\x00", '', $trace['class']); |
There was a problem hiding this comment.
Shouldn't that be its own PR?
There was a problem hiding this comment.
Right now, this is not doing any harm. When we adjust the table type to jsonb Postgres checks if the json is valid and doesn't like null bytes in there.
I don't think that this must be in a separate bugfix PR but I could extract it. The only thing is if the user already has null bytes in the table. Then he would need to remove them. Or do you have a case in mind?
|
New version for dbal was made which makes this change easier for our users. Still need to evaluate if this is worth it due to slower write speed compared to the only limited gain for querying the eventstore. |
|
I rebased this PR and would like to investigate into this again in the next days/weeks. |
We should use
jsonbwhen the user is using postgresql. This give the user better query capabilities on the json fields in the store.When this PR is released doctrine/dbal#6693 the migration tooling should pick this change up. So the user does not need to update the table themselfes besides of the normal call to
bin/console do:mi:di&bin/console do:mi:mi.