-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
SQL Server/TinyTDS Error for OCTET_LENGTH #35
Comments
Hey @utsw-alex-williams, I have no experience with MSSQL unfortunately so I can tell you little at the moment. I have just opened an experimental PR here: #38 I'll try something when possible 🤷 |
After checking the failing specs:
I added a new commit on the PR 38 to apply these changes. Can you make a try using the branch feat/mssql-support ? |
So far it looks like that worked perfectly. There were no problems displaying a variant with Vips transformations. Thank you so much! |
@utsw-alex-williams: I have just released the version 1.3.0 which includes the experimental MSSQL support, can you make a test and let me know? |
Looks great! |
A special thanks to @utsw-alex-williams for the support! 💪 FYI: I've also updated a test to include variants: |
Hello, and thank you for creating this gem - it has been very useful.
I am using ActiveStorageDB with SQL Server via TinyTDS. I'm aware that ActiveStorageDB currently specifies support for Postgres and MySQL only, but I figured I'd ask if SQL Server could be considered for future support, or if you have any insight into a possible workaround for my specific issue.
I am encountering errors when attempting to use ActiveStorage variants with ActiveStorageDB. I got an error related to AnalyzeJob after attaching images via ActiveStorage, but displaying images was ok. However, the same error occurs when attempting to display variants. The error displayed is:
The SQL statement causing this issue is:
I think SQL Server has either LEN or DATALENGTH, though without deep diving into the code I'm not sure which would be better to use, if any, or if it could be easily patched in.
I understand that SQL Server is not officially supported but any guidance on how to fix this would be appreciated.
The text was updated successfully, but these errors were encountered: