Thanks! No worries will turn it into a PR next time.
Matt
On Monday, March 10, 2014 2:06:14 PM UTC+13, Massimo Di Pierro wrote:
>
> fixed in trunk. thanks for the patch.
>
> On Saturday, 8 March 2014 21:40:35 UTC-6, Matt wrote:
>>
>> Attached code change to the issue also
>>
>> On Sunday, March 9
fixed in trunk. thanks for the patch.
On Saturday, 8 March 2014 21:40:35 UTC-6, Matt wrote:
>
> Attached code change to the issue also
>
> On Sunday, March 9, 2014 4:25:26 PM UTC+13, Matt wrote:
>>
>> Thanks... Have raise an issue:
>>
>> https://code.google.com/p/web2py/issues/detail?id=1897
>>
>>
Attached code change to the issue also
On Sunday, March 9, 2014 4:25:26 PM UTC+13, Matt wrote:
>
> Thanks... Have raise an issue:
>
> https://code.google.com/p/web2py/issues/detail?id=1897
>
> On Sunday, March 9, 2014 3:47:08 PM UTC+13, Anthony wrote:
>>
>> Good point. Maybe submit a Google Code i
Thanks... Have raise an issue:
https://code.google.com/p/web2py/issues/detail?id=1897
On Sunday, March 9, 2014 3:47:08 PM UTC+13, Anthony wrote:
>
> Good point. Maybe submit a Google Code issue (or better yet, a patch).
>
> Anthony
>
> On Saturday, March 8, 2014 9:44:03 PM UTC-5, Matt wrote:
>>
>
Good point. Maybe submit a Google Code issue (or better yet, a patch).
Anthony
On Saturday, March 8, 2014 9:44:03 PM UTC-5, Matt wrote:
>
> Hey Anthony,
>
> Thanks for your reply.
>
> Yes. We're using a custom method of user registration. When the process
> finishes the value is then set to null
Hey Anthony,
Thanks for your reply.
Yes. We're using a custom method of user registration. When the process
finishes the value is then set to null.
Thought it would be prudent to raise this as the auth_user table should be
sturdy enough to handle this type of value.
it would only be a small
6 matches
Mail list logo
