View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
03468Bug reportsOtherpublic2009-07-10 15:472009-08-03 09:22
Reporteruser4054Assigned Toc_schmitz  
PrioritynormalSeveritytrivial 
Status closedResolutionfixed 
Product Version1.85+ 
Fixed in Version1.85+ 
Summary03468: Error while exporting survey structure
Description

I have a survey which is not activated yet, before activating it I wanted to export my survey structure so I selected .csv file extension and tried it but I got the following error. I tried several times but no luck.

[Microsoft][ODBC SQL Server Driver][SQL Server]El tipo de datos text no se puede seleccionar como DISTINCT porque no es comparable.:SELECT DISTINCT srvy_question_attributes.* FROM srvy_question_attributes, srvy_questions WHERE srvy_question_attributes.qid=srvy_questions.qid AND srvy_questions.sid=73817

(translation: text data type can not be selected using DISTINCT because it is not comparable)

Im using limesurvey 1.85+ and MS SQL Server 2005.

Additional Information

It is due to the data type of one of the fields in the SELECT clause, text data types are not allowed in combination with DISTINCT clause, to correct this error we should change the data type of that perticular field.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)
I will donate to the project if issue is resolved
Browser
Database type & versionMS SQL Server 2005
Server OS (if known)Windows XP Prof
Webserver software & version (if known)IIS 5.1
PHP Version5.2.10

Users monitoring this issue

There are no users monitoring this issue.

Activities

user372

2009-07-10 16:05

  ~08821

@ c_schmitz: can you reproduce the issue with MS SQL?
bobc55

bobc55

2009-07-10 23:20

reporter   ~08823

I thought we changed the data type and or php in a previous version

The error is because of Microsoft SQL Server. You cannot have a distinct with a text data type.

In database version 135 it was changed to TEXT.

The workaround it to change it to a varchar(8000) for sqlserver 2000 or varchar(max) for sqlserver 2005.

Issue History

Date Modified Username Field Change
2009-07-10 15:47 user4054 New Issue
2009-07-10 15:47 user4054 Status new => assigned
2009-07-10 15:47 user4054 Assigned To => user372
2009-07-10 15:47 user4054 Database & DB-Version => MS SQL Server 2005
2009-07-10 15:47 user4054 Operating System (Server) => Windows XP Prof
2009-07-10 15:47 user4054 Webserver => IIS 5.1
2009-07-10 15:47 user4054 PHP Version => 5.2.10
2009-07-10 16:05 user372 Note Added: 08821
2009-07-10 16:05 user372 Assigned To user372 => c_schmitz
2009-07-10 23:20 bobc55 Note Added: 08823
2009-08-02 22:34 c_schmitz Status assigned => resolved
2009-08-02 22:34 c_schmitz Fixed in Version => 1.85+
2009-08-02 22:34 c_schmitz Resolution open => fixed
2009-08-03 09:22 c_schmitz Status resolved => closed
2010-05-06 10:27 c_schmitz Category Import / Export => (No Category)