Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
The module uses the creatino of tables by means of:
CREATE TABLE {XX} SELECT ....
This is not compatible with SQL Server.
I fixed it, patch provided.
I have also seen that, on the same file, there is a similar problem somewhere else but I have no time to fix.
Comment | File | Size | Author |
---|---|---|---|
#3 | views_data_export-sqlsrv_batch_compatibility-2015361-3.patch | 5.79 KB | ruloweb |
views_data_export_plugin_display_export.inc_.patch | 1.51 KB | david_garcia | |
Comments
Comment #2
david_garcia CreditAttribution: david_garcia commentedComment #3
ruloweb CreditAttribution: ruloweb commented@david_garcia thanks for your fix! it works ok for me too.
I created another version which creates the class views_data_export_plugin_query_sqlsrv_batched with the small fix. Notice that for pgsql there is a different CREATE TABLE implementation too, so the module maintainer created the views_data_export_plugin_query_pgsql_batched class to address that, maybe this is what you see has a different problem.
I also forced the query to run always $query->range(), because when the views has an order by clausule, it will throw:
Thanks!
Comment #4
ruloweb CreditAttribution: ruloweb commentedComment #5
sosyuki CreditAttribution: sosyuki commented@ruloweb thanks for your fix! it works ok for me.