It works like a charm. :)
Thanks a lot for your help guys. I would have never figured it out by
myself!
Have a wonderful Friday!
David
On 12 October 2012 00:34, Niphlod wrote:
> you're overridding the default validator (IS_DATE*) with IS_NOT_EMPTY
>
> replacing this line
> db.news.date_lo
you're overridding the default validator (IS_DATE*) with IS_NOT_EMPTY
replacing this line
db.news.date_local.requires = IS_NOT_EMPTY()
with
db.news.date_local.requires.append(IS_NOT_EMPTY())
should work.
--
Not a problem! ;)
Here the *model*:
> db.define_table('news',
> Field('title', 'string'),
> Field('body', 'text'),
> Field('date_local', 'datetime'),
> Field('date_utc', 'datetime', readable=False, writable=False)
> )
>
> db.news.title.requires = [IS_NOT_EMPTY(), IS_NOT_IN_DB(db,
We need to see some of the code. Somehow the validator is not called.
On Thursday, 11 October 2012 13:32:40 UTC-5, David Sorrentino wrote:
>
> I'm using a custom form, but no custom validators.
> Do you need some additional information?
>
> Cheers,
> David
>
>
> On 11 October 2012 15:34, Massimo D
I'm using a custom form, but no custom validators.
Do you need some additional information?
Cheers,
David
On 11 October 2012 15:34, Massimo Di Pierro wrote:
> Is it possible you have a custom validator?
>
> is should have a IS_DATE validator (default). It is the validator that
> maps request.va
Is it possible you have a custom validator?
is should have a IS_DATE validator (default). It is the validator that maps
request.vars.date into form.vars.date and performs the conversion.
On Thursday, 11 October 2012 06:30:46 UTC-5, David Sorrentino wrote:
>
> Changed the name of the field from "
Changed the name of the field from "date" to "created_on" to avoid
confusion.
Tried with a fresh table.
Result:
*form.vars.created_on* seems to be still an object of type str.
Am I missing something? :-/
Cheers,
David
On 11 October 2012 11:45, Niphlod wrote:
> uhm. I can't reproduce the issue
uhm. I can't reproduce the issue. For me form.vars.whatever if is a field
of type datetime is a datetime tuple. Request.vars.whatever on the other
hand is always a string, as it should be.
Try with a fresh table
PS: having a db with a column named "date" is a call for problems ...
On Thursday
Thanks for your explanation Niphlod. ;)
I'm trying to normalize the time, as you suggested.
However I'm facing some difficulties.
In particular I created an additional field in my table to store the
normalized time (UTC) too. So now my table looks like that:
> db.define_table('news',
> Field
Also if it makes you feel better LinkedIn hasn't implemented this
properly either :P
On Wed, Oct 10, 2012 at 10:57 PM, Niphlod wrote:
> welcome to datetime madness :D It's exactly what you need to take into
> consideration if you're working with user-inputted datetimes. You'd need to
> retrieve i
welcome to datetime madness :D It's exactly what you need to take into
consideration if you're working with user-inputted datetimes. You'd need to
retrieve it's local date (javascript comes to the rescue, or based on
nation, or whatever) and calculate the difference between that and your
curren
I see your point, but what if the user inserts into the datetime input
field his/her current time? It will be different from the server's one
(which I set to GMT), and prettydate will not work properly.
I confess that I am a bit confused about that.
Best,
David
On 10 October 2012 11:16, Niphlod
not necessarily wrong, just a different timezone. If you're going to
display "prettydates" just in the browser for a "nicer visualization" you
should take into consideration that your server's locatime can be different
from the users's browser one.
In a "perfect" setup, your server is on GMT (
Hey Niphlod,
Thank you for your help.
The version is 2.0.9 (2012-10-05 09:01:45) dev
I tried datetime.datetime.now() in my application and I just discovered
that it is 2 hours late. This explains why prettydate is then 2 hours in
hurry!
The odd thing is that if I open a python console and try
da
should calculate the difference between datetime.datetime.now() and your
date. what web2py version are you using ?
On Wednesday, October 10, 2012 10:16:24 AM UTC+2, David Sorrentino wrote:
>
> Hello everybody,
>
> I am using the module *prettydate*, but it seems that it matches the
> datetime I
15 matches
Mail list logo
