Password saving fails due to Binary column type
See original GitHub issueMaybe some compatibility stuff is needed here, because this commit 570d5bc587cc029878d18dd74e0044e71104ce91 made impossible to save a password on PostgreSQL 9.5 (Python 3.6). Getting TypeError: can't escape str to binary
.
Or at least a comment there to lower the debugging time. What do you think?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Password saving fails due to Binary column type #158 - GitHub
A solution to this would be to eliminate the __init__ method of the model altogether (we shouldn't be overriding it without good reason)...
Read more >saving and comparing passwords to database as binary using ...
Save this question. Show activity on this post. In an ASP.NET application, I have saved a password to the database as "Binary" data...
Read more >How to fix the error "String or binary data would be truncated"
To fix this error, patch to SQL Server 2016 SP2, CU6 or newer (including SQL Server 2017), and then turn on trace flag...
Read more >binary and varbinary (Transact-SQL) - Microsoft Learn
When converting data from a string data type to a binary or varbinary data type of unequal length, SQL Server pads or truncates...
Read more >11.3.3 The BINARY and VARBINARY Types
The BINARY and VARBINARY data types are distinct from the CHAR BINARY and VARCHAR BINARY data ... an attempt to store 'a\0' causes...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing, as this issue is stale. Feel free to reopen or comment if there’s still an issue.
@sloria Sorry about that! Yeah, I did that from my phone using MGit, which is very limited in it’s behavior. I have cleaned up that branch, updated all related tests, and opened #1195 😄