Skip to content
New issue

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

Performance killer: SQL query using nvarchar instead of char #217

Open
shubmitt opened this issue Jun 4, 2020 · 0 comments
Open

Performance killer: SQL query using nvarchar instead of char #217

shubmitt opened this issue Jun 4, 2020 · 0 comments

Comments

@shubmitt
Copy link

shubmitt commented Jun 4, 2020

This issue has been posted here. I believe it has carried over from this library. So sharing here also.

ESSolutions#50

An example query where conversion is happening -

(@p3 nvarchar(64),@P4 nvarchar(64),@p1 int,@p2 datetime2(7))UPDATE [transactions_transaction] SET [is_split_transaction] = @p1, [modified] = @p2 WHERE ([transactions_transaction].[transaction_id] = @p3 AND [transactions_transaction].[user_id] = @P4)

both user_id and transaction_id are CustomUUIDField (char(32)) and we dont want pyodbc to convert this params

@shubmitt shubmitt changed the title SQL query using nvarchar instead of char Performance killer: SQL query using nvarchar instead of char Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant