Comment: Re:Caching doesn't need email (Score 1) on 2010.08.10 3:11
I guess that is progress. We have gone from supporting offline reports now to supporting offline reports in the future and all we have to do is wait from someone to write code.
I guess that is progress. We have gone from supporting offline reports now to supporting offline reports in the future and all we have to do is wait from someone to write code.
This sounds like something growl would be a decent match for. I have not used it myself but Growl::GNTP should let you send notifications to growl from perl.
I think if you want some information about customers it is probably a bad idea not grouping by customer id. Depending on your site you may or may not have 2 customers with the same name but you will almost always have the occasional repeat customer.
Actually , looking at the code I would assume I misunderstood the requirements as I don't see why order_date is there at all.
To me it seemed more like people have moved from what and when to an all round encompassing negativity.
Have you tried http://www.bulmers.ie/about-us/pear.asp
Padre seems to have a fatal dislike for things that are not perl scripts. If I try to create anything else I get 'C:\Documents and Settings\PSinnott>Can't locate object method "mime_type_by_exte
nsion" via package "Padre::Document::Perl" at C:/strawberry/perl/site/lib/Padre/
Wx/Main.pm line 4022.'
It is more pervasive than just the single spot.
Adding || $@ =~
I think using $! in numeric context gives access to the errno value which would be portable between locales but you may need some help from IO::Pty in order to get access to that.
That's right, that's how change happens. To use a not-quite-accurate analogy, he saw p5p as damage and routed around it.
You may not like what he is asking for, but there's nothing at all wrong with his tactics.
If you want to route around the people who maintain a piece of software why not just fork and be done with it?
I tend to prefer shared over local as long as the shared resources are in the same office and have reasonable rights. Servers located in different continents or where I have not got enough rights to do my job are a pain.
If your test db servers are down as often as they are up, 20 is a normal load on your server or you often don't have network connectivity in your office then you probably have bigger problems than the relative merits of centralized verses distributed development.