The ticket issues is definitively a bug introduced in trying to parse
ipv6 addresses. I reposted a fix in trunk. Please try reproduce the
same errors and see if you can see the tickets. let me know.
Once this is settled....
if db.table.field is an integer, by defaul, it requires an int value.
db.table.field.requires=IS_NULL_OR(IS_ALPHANUMERIC)
causes the ticket because it is incompatible with the field being an
integer.
You can do
db.table.field.requires=IS_NULL_OR(IS_INT_IN_RANGE(-100,100))
I think this is what you want.
Massimo
On Jan 4, 9:00 am, Fran <[email protected]> wrote:
> If I define 1 of my fields as being of type 'integer' then that means
> that it makes the field mandatory (in T2 at least).
> If I define a db.table.field.requires=IS_NULL_OR(IS_ALPHANUMERIC)
> then this allows me to submit Empty fields & prevents me from entering
> non-numeric digits, however if I do enter a digit then it refuses to
> accept the form & the
> generated ticket refuses to display.
> It generates it in the format:
> application/.2009-01-04.14-55-07.cce20779-a2e1-4c39-9444-0f0018352a08
> instead of the usual
> application/127.0.0.1.2009-01-04.14-55-07.cce20779-
> a2e1-4c39-9444-0f0018352a08
>
> So If I try to follow this I just get
> Invalid request
>
> However if I add the 127.0.0.1 back in manually I get an:
> Internal error
> with a new ticket generated in the bad format. (application =admin
> this time)
>
> This is latest Trunk.
>
> F
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
