birthday datatype

Friday 13 August 2004 8:44:46 am

Great work Emil,

This will solve the birthday problems with >34y guys/girls.

I'll also pursue a "long" datetime datatype

Tx

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Saturday 14 August 2004 12:03:11 pm

The testing I did with with ADOdb was largely successful, only it didn't improve anything;-)

The debug output would complain about missing arguments probably because all params in adodb_mktime were compulsory, this improved with the latest release where only "hour, min, secs is compulsory", but those are the ones not used in eZP (from what I understand). I showed the code to a guy I know that actually know programming and he said that all params were declared (right word?) although half of them with "0" which probably is the problem. I was suppose to show him the actual debug, but then came the nice weather here in Norway and I took a holiday, and here comes Emil and solves it all!

I suppose we can conclude that the current ADOdb can't be implemented without some hacking, but the way I understand it, it is the authors intention to make it in line with the standard mktime. Actually it took 5 days from my first post at his fora to he released an improved (but not compatible) version.

Thank you for your solution Emil!
Are there any disadvantages to the birthday datatype and the date datatype? What date-range does it support?

Wednesday 08 September 2004 1:30:39 am

had the problem with birthdates before 1970 when we switched from Red Hat 7 to Fedora Core 1.

I am using <b>adodb_mktime()</b> and it is working fine now.

Tuesday 12 October 2010 7:13:22 am

I just saw this thread so my response is probably to late. However, I have the same problem when storing a date of birth for people as objects. Thus I created a data type that is 'date as text'. It works by storing xml text of the applicable information. It will also use the year (if entered) as the sortable field. I set it up so that if you mark it as required then there is different data that is required.

-> For instance if the dob is required you must at least enter a year.

-> If you have a year, then you can enter in a month.

->If you have a month then you can enter in a date.

So this will prevent someone from entering in just a date and nothing else, or date and year. I have the data type ready, but I'll wait to see if anyone is interested in it.