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?
|