I think that rather than just making loud, sometimes irrelevant statements, you should focus on your survey designs, not the perceived limitations of the platform.

If you think you can improve LS, you are welcome to submit pull requests.

If this is perceived, should take care of innocent user, remind first and fix the bug ASAP.

Just in my eyes, this guy(girl?) help to find a bug, your brashness say no to those developer help.

vest of a loyal user from 1.9

Welcome Robert(k),

I assume you've around 5 years experience with LimeSurvey without any major encountered issue, if you are a "loyal user from 1.9" and if this is your 1st participation in this active forum where problems are usually discussed and solved… This sounds very good and it will be particularly valuable for all the LimeSurvey community (developers & users) if you can (in a few words) describe how you are using the software (context/purpose) & your personal overall opinion (pro & cons) ?

I am also asking myself how someone wants to create a database design that DOESN'T use one column per question. I am not a database expert, but I would love to hear how this could be improved. Would be very interesting. Maybe one of those database experts could explain this in detail.

Since iscar has posted in this thread that he has changed from Limesurvey to another tool, you might no longer get an answer from iscar.

1.) A warning is not that simple, since different database servers are coming up with different limits. No simple rule of thumb or easy checking.

It isn't a big issue if you backup your surveys. I wonder what kind of surveys are designed.
Before they reach the limit they will get slow. The main purpose of LimeSurvey is asking questions in form of a survey. Sometimes it look that they want to design a data input tool with very big array questions and other things which would raise the dropout rate in a typical survey situation up to 100%.

There is always room to improve the database model.

2.) If there is room for a database design discussion take a look at
stackoverflow.com/questions/1764435/data...-design-for-a-survey

www.limesurvey.org/manual/Database_Stora...t_M1_Database_Design

I Closed your post in SO, had been entertained.
1.read it first, How number of columns affects performance?

2.When tables get too many columns,technically speaking, it's a design flaw.
Even limit is 4096,it's seldom to see a table columns>60.no engineer would like to design wide table.
It absolutely cause performance problem, and many unpredictable issues even crash. Cases I experienced such as backup database but it contain inconsistent data.

3.
when create those wide facts table, always "vertical split" wide table to several thin tables with the same primary key-id.
Normally revise 3 places: Try it, 30mins code work.

Btw, users reminder is always been appreciated.

misys wrote: ....
Try it, 30mins code work.

Btw, users reminder is always been appreciated.

Hi,

You can patch the next Major LimeSurvey release, Sam is worjing on it, and we need help to get quick. github.com/SamMousa/LimeSurvey

Remind :
- need to work on more SQL the mySQL only
- need to be easily updatable (when we all our old user's update 1.90 version for example)
- need to be maintainable

We have a project to do big optimisation on SQL table, need some times. Maybe if we sell LimeSurvey a lot of money ....

@misys: How much is your hourly rate? If this really is just 30min code work, I guess I could sponsor this feature. Not that I need it much, but I ran in the database column limit once, with a survey that had loads of multiple answer questions, with long answer lists. So it would be interesting.

I am sure that the limesurvey developers wouldn't mind implementing this in 2.06 if we could get this running in the next 2 weeks (any feedback on that?).

Could you let me know when you would be able work on this and what the total cost would be for this?

Since iscar, robertk and misys are one person I wouldn't expect too much interaction.

But let me quote DenisChenu who once told me about problematic Wordpress plugins: "use a plugin make by a good dev".
Transfer that remark to survey systems and you have nothing to fear.

DenisChenu wrote:

misys wrote: ....
Try it, 30mins code work.

Btw, users reminder is always been appreciated.

Hi,

You can patch the next Major LimeSurvey release, Sam is worjing on it, and we need help to get quick. github.com/SamMousa/LimeSurvey

Remind :
- need to work on more SQL the mySQL only
- need to be easily updatable (when we all our old user's update 1.90 version for example)
- need to be maintainable

We have a project to do big optimisation on SQL table, need some times. Maybe if we sell LimeSurvey a lot of money ....

Hi,

I am willing to help you.
It's quick to paste the vertical split paradigm.Since I never engaged in this project, most of time spend on reading the original code.
I skimmed through the 2.05 version last weekend, have no experience on the 1.90 version.

It's bold idea that maintain multi subversions at the same time. I guess 1.90 version has something special thus still been maintained. I suggest to pack the files need to be revised of each subversion.

Btw, based on my understanding, update script always based on the latest version. It's easy to find the update problem and minimize the update script.

@holch, I am misys, cannot login that account.

Pls pack the files need to be revised with your requirement, my mail:misys linuxmail.org

I think you are the leader of this project, but your speaking smell weird and it seemed you know little about database. I am not sure your authenticity.
Btw, freelancer.com is open for you.

Uhhh, dunnt understand what you said.
If any further question, please mail me.