Thank you! That is a great hint!!
On Fri, Mar 8, 2013 at 11:04 AM, Niphlod wrote:
> Ok, got it. it's not the scheduler's table you want with the booleans to
> work, it's the things the scheduler execute that needs to interact with
> some other tables in the environment...to be polite, that li
Please open a ticket about this.
On Friday, 8 March 2013 02:28:13 UTC-6, Massimiliano wrote:
>
> Is there any chance to take a look on this problem?
>
> Thank you
>
>
>
> On Mon, Feb 25, 2013 at 7:42 PM, Massimiliano
> > wrote:
>
>> Hi,
>> I'm working on a legacy database where all boolean are ma
Ok, got it. it's not the scheduler's table you want with the booleans to
work, it's the things the scheduler execute that needs to interact with
some other tables in the environment...to be polite, that little hack you
do is nice, but not "the recommended way" this is a case for your own
cu
The need of smallint as boolean is required for my application...
I don't knows if the word "legacy" is correct, I can't change the table
structure but I can insert and delete records...
In any case I expect that running ./web2py.py-K logistica it reads my db.py
and my defines.
What's happen if my
deviating from the standards can be a pain, but if you set the migration
off, change your column datatype outside web2py, the default typecasting
would kick in and it should work anyway.
PS: legacy db is where there are yet tables you can't change. The scheduler
creates its own tables, so wh
Hi,
I'm working on a legacy database where all boolean are mapped to 0, -1.
In my application I redefine adapter TRUE/FALSE as saw in this group.
In db.py:
db = DAL('postgres://postgres@127.0.0.1/logistica')
import copy
db._adapter.types = copy.copy(db._adapter.types)
db._adapter.types['boolea
6 matches
Mail list logo
