Radicore Forum: How To » overruling primary validation time fieldtype

Home » RADICORE » How To » overruling primary validation time fieldtype

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

overruling primary validation time fieldtype [message #454]

Tue, 12 December 2006 07:51

johandewit
Messages: 25
Registered: May 2006
Location: Belgium

Junior Member

Hi,

I want to be able to enter a time value > 24 hours.
During insert/update, this will generate an error "Invalid HOURS", because the std.datevalidation.class only allows hours <= 24.

It seems this 'primary validating rule' cannot be skipped/overruled.

What is the best and/or proper way to achieve this, without making any modification to the framework code.

Thanks

Report message to a moderator

Re: overruling primary validation time fieldtype [message #455 is a reply to message #454]

Tue, 12 December 2006 11:05

AJM
Messages: 2382
Registered: April 2006
Location: Surrey, UK

Senior Member

Unfortunately the TIME data type is currently limited to 00:00:00 to 23:59:59 as I have only ever used it to represent time of day, not elapsed time. As MySQL supports values in the range '-838:59:59' to '838:59:59' I shall put this on my 'to do' list. I'm not sure if PostgreSQL allows such values, and I know Oracle does not have a TIME type at all.

In the mean time you may find it easier to change your data type to NUMERIC instead of TIME, then you can allow for any number of hours.

Tony Marston
http://www.tonymarston.net
http://www.radicore.org

Report message to a moderator

Previous Topic:	Concurrency / freshness of data objects
Next Topic:	Tutorial - problem??

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jul 06 00:13:22 EDT 2025

Total time taken to generate the page: 0.10185 seconds