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
Long story short, we are using debug to print SQL queries that are executed against database servers and whenever people use a like or ilike query in combination with % at the beginning, it sometimes happens that the logs show NaN. This happens when the search term starts with any of the printf-style characters, e.g. for something like SELECT * FROM foo WHERE name LIKE %fauzi%. The logs will then contain NaNauzi.
Would it be possible to force a debug log statement to ignore any printf formatting?
We are seeing some interesting side-effect of the printf-style feature outlined here: sequelize/sequelize#17448
Long story short, we are using debug to print SQL queries that are executed against database servers and whenever people use a like or ilike query in combination with % at the beginning, it sometimes happens that the logs show
NaN
. This happens when the search term starts with any of the printf-style characters, e.g. for something likeSELECT * FROM foo WHERE name LIKE %fauzi%
. The logs will then containNaNauzi
.Would it be possible to force a debug log statement to ignore any printf formatting?
Something like:
The text was updated successfully, but these errors were encountered: