Why can' t you use the already pre-defined id field? You don't need to
define a new one, every table already has and and id field with name
"id".
Fabiano.
On Sat, Jan 15, 2011 at 6:37 AM, Rick <sababa.sab...@gmail.com> wrote:
> So the problem was that the controller file line creates an error when
> I
> add the 'id' field and 'migrate=False' to the day table. Here is some
> more code:
>
> ===in the model file===
> import datetime
> now = datetime.date.today()
> db.define_table('day',
> Field('the_id', 'id'),
> Field('thedate','date', default=request.now),
> Field('value', 'integer'),
> migrate=False)
>
> ===in the controller file===
> records = db().select(db.day.ALL, orderby=db.day.thedate)
>
> On Jan 15, 8:16 am, Kenneth Lundström <kenneth.t.lundst...@gmail.com>
> wrote:
>> Could you shows us the relevant part of your models file, where the
>> table is defined and then also the error ticket.
>>
>> Kenneth
>>
>>
>>
>>
>>
>>
>>
>> > Thanks for the suggestion! The 'id' field looks like a smart solution.
>> > But there seem to be a problem -- This line creates an error when I
>> > add the 'id' field and 'migrate=False' to the day table:
>> > records = db().select(db.day.ALL, orderby=db.day.thedate)
>> > Any ideas?
>>
>> > On Jan 4, 4:03 am, Fabiano<fabianoeng...@gmail.com> wrote:
>> >> What stops you from using 'id' field?
