You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DjDT currently doesn't support PostgreSQL Array syntax and returns 500 when trying to analyze or reselect queries that contain Postgres arrays in params.
From the looks of it DjDT query tracker assumes no nested values when serializing query params. The error occurs when these incorrectly serialized params are fed into the cursor.
The text was updated successfully, but these errors were encountered:
@aaugustin Do you know if there was a reason why we chose to create our own _decode rather than pickling the params? I'm thinking we may want to convert to pickling the params since the range fields need to have the actual class instance passed as the parameter.
Right now the toolbar is decoding a parameter of (NumericRange(0, 999999, '[)'),) to be '["NumericRange(0, 999999, \'[)\')"]' which when the form cleans and outputs the parameters it becomes "NumericRange(0, 999999, \'[)\')"
DjDT currently doesn't support PostgreSQL Array syntax and returns 500 when trying to analyze or reselect queries that contain Postgres arrays in params.
From the looks of it DjDT query tracker assumes no nested values when serializing query params. The error occurs when these incorrectly serialized params are fed into the cursor.
The text was updated successfully, but these errors were encountered: