No hard feelings, the coding was very simple and out of the box, performing 
perfectly until ....
But I agree, not a really production proof design.

I already redesigned the functionality using SQLFORM.factory and using an 
existing table for the time-sequences.

On Tuesday, September 23, 2014 9:10:17 PM UTC+2, Niphlod wrote:
>
> sorry for being - probably - overzealous, but you're not trying to create 
> a table with 2 columns with an indefinite number of rows. You're doing the 
> exact opposite: creating a table with an indefinite number of columns. This 
> is confirmed by the fact that the variable in your code is indeed 
> *issue_var_field and the error you're facing (if you care to read mysql 
> manual, you'll find about innodb storage per-row limitations).
> At this point, I strongly suggest to reengineer your code to use a fixed 
> number of columns ^_^'
>
> On Tuesday, September 23, 2014 5:09:56 PM UTC+2, Richard wrote:
>>
>> Leonel,
>>
>> You are right, the most important message you and Niphlod give me is the 
>> bad design of the dynamic tables and the need for migration=True.
>> Is this conclusion correct?
>>
>> If so, I'll redesign the functionality towards a table containing the 
>> time sequences and the relation to a table with the meta data.
>>
>> regards,
>> Richard D
>>
>> On Tuesday, September 23, 2014 4:54:56 PM UTC+2, Leonel Câmara wrote:
>>>
>>>  table per time sequence is needed because I want to have security 
>>>> levels on those table devided in view and edit.
>>>
>>>
>>> Why do you need a new table for that? You can create whatever 
>>> permissions you want, if you need you can create read and update 
>>> permissions per record.
>>>
>>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to