We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
to_char
see #7351 (comment).
build_to_char_const_tmpl
The text was updated successfully, but these errors were encountered:
suspect simply because chrono::format::Item is not efficient enough https://github.com/chronotope/chrono#:~:text=(while%20not%20being%20the%20primary%20goal)%20reasonably%20efficient
chrono::format::Item
Sorry, something went wrong.
Update, to_char is not really a performance bottleneck, only ~1% is attributed to it in q17.
However, to_char does lead to things being represented as varchar, which is the real cost.
varchar
Opening a separate issue to track.
kwannoel
No branches or pull requests
see #7351 (comment).
build_to_char_const_tmpl
w/o template string. I think what is currently benched includes compilation of template str.Precompute and store in executor the tmpl pattern matching object.This is done already.The text was updated successfully, but these errors were encountered: