the recommended way to use big-something is DAL(bigint_ID=True), however,
I'm not sure it will trigger a migration.
I'd certainly avoid migrating the PK to another type while the table is
full of zillions rows.
Are you trying to migrate an existing table or you're creating it brand new
?
On Tuesday, April 30, 2013 10:29:00 AM UTC+2, Johann Spies wrote:
>
>
> After running into a 'integer out of range' problem in Postgresql I was
> expecting this addition to my table definition to change the postgresql
> definition of the id-field to 'bigint' but it did not happen:
>
> db.define_table('rkeywords',
> Field('id', type = 'big-id'),
>
> but this did not change:
>
> \d isi.rkeywords;
> Table "isi.rkeywords"
> Column | Type | Modifiers
>
>
> ---------+-----------------------+------------------------------------------------------------
> id | integer | not null default nextval(
> 'isi.rkeywords_id_seq'::regclass)
>
>
> So how do I get web2py to alter the postgresql-definition to bigint?
>
> Regards.
>
> Johann
>
>
--
---
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/groups/opt_out.
