Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Paul McGarry
On Fri, Mar 1, 2013 at 9:49 PM, Richard Quadling wrote: > Hi. > > My heads trying to remember something I may or may not have known to start > with. > > If I hold datetimes in a DB in UTC and can represent a date to a user > based upon a user preference Timezone (not an offset, but a real > timez

Re: [PHP] Introduction ... !

2013-03-01 Thread Nick Whiting
On Fri, Mar 1, 2013 at 6:32 PM, tamouse mailing lists < tamouse.li...@gmail.com> wrote: > On Fri, Mar 1, 2013 at 11:56 AM, Daniel Brown wrote: > > On Fri, Mar 1, 2013 at 12:54 PM, Jim Giner > wrote: > >> > >> What gives you such optimism? I recently saw a list of languages in > use and > >> PHP

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Nick Whiting
On Fri, Mar 1, 2013 at 7:04 PM, Sebastian Krebs wrote: > 2013/3/2 tamouse mailing lists > > > On Fri, Mar 1, 2013 at 11:53 AM, Matijn Woudt wrote: > > > On Fri, Mar 1, 2013 at 11:49 AM, Richard Quadling > >wrote: > > > > > >> Hi. > > >> > > >> My heads trying to remember something I may or may

Re: [PHP] Finding an Address

2013-03-01 Thread Tedd Sperling
On Feb 28, 2013, at 12:36 PM, Floyd Resler wrote: > I have a project where my client would like to find the nearest street > address from where he current is. Getting the longitude and latitude is easy > enough but I'm having a hard time finding out how to get the nearest house. > I have fou

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Sebastian Krebs
2013/3/2 tamouse mailing lists > On Fri, Mar 1, 2013 at 11:53 AM, Matijn Woudt wrote: > > On Fri, Mar 1, 2013 at 11:49 AM, Richard Quadling >wrote: > > > >> Hi. > >> > >> My heads trying to remember something I may or may not have known to > start > >> with. > >> > >> If I hold datetimes in a D

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread tamouse mailing lists
On Fri, Mar 1, 2013 at 11:53 AM, Matijn Woudt wrote: > On Fri, Mar 1, 2013 at 11:49 AM, Richard Quadling wrote: > >> Hi. >> >> My heads trying to remember something I may or may not have known to start >> with. >> >> If I hold datetimes in a DB in UTC and can represent a date to a user >> based up

Re: [PHP] Introduction ... !

2013-03-01 Thread tamouse mailing lists
On Fri, Mar 1, 2013 at 11:56 AM, Daniel Brown wrote: > On Fri, Mar 1, 2013 at 12:54 PM, Jim Giner > wrote: >> >> What gives you such optimism? I recently saw a list of languages in use and >> PHP has dropped quite a bit over the last 5 or more years. >> Being a relative newbie myself, I'm happy

Re: [PHP] Close enough to Friday...

2013-03-01 Thread tamouse mailing lists
On Thu, Feb 28, 2013 at 9:59 PM, Adam Richardson wrote: > On Thu, Feb 28, 2013 at 10:19 PM, tamouse mailing lists > wrote: >> >> Congratulations on ditching the Dreamweaver Templates! >> >> Now, as to preprocessing: how does this benchmark out? Have you >> noticed a significant different in proce

Re: [PHP] Introduction ... !

2013-03-01 Thread Daniel Brown
On Fri, Mar 1, 2013 at 12:54 PM, Jim Giner wrote: > > What gives you such optimism? I recently saw a list of languages in use and > PHP has dropped quite a bit over the last 5 or more years. > Being a relative newbie myself, I'm happy that PHP exists and is so readily > available to us hobbyists,

Re: [PHP] Introduction ... !

2013-03-01 Thread Jim Giner
On 3/1/2013 12:43 PM, Daniel Brown wrote: On Fri, Mar 1, 2013 at 10:57 AM, Nick Whiting wrote: Hello PHP'ers! Just thought I would introduce myself to the mailing list since I've worked with PHP for almost 10 years now and yet haven't really been community active ... I've developed quite a fe

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Matijn Woudt
On Fri, Mar 1, 2013 at 11:49 AM, Richard Quadling wrote: > Hi. > > My heads trying to remember something I may or may not have known to start > with. > > If I hold datetimes in a DB in UTC and can represent a date to a user > based upon a user preference Timezone (not an offset, but a real > timez

Re: [PHP] Introduction ... !

2013-03-01 Thread Daniel Brown
On Fri, Mar 1, 2013 at 10:57 AM, Nick Whiting wrote: > Hello PHP'ers! > > Just thought I would introduce myself to the mailing list since I've worked > with PHP for almost 10 years now and yet haven't really been community > active ... > > I've developed quite a few open-source projects over the y

[PHP] Introduction ... !

2013-03-01 Thread Nick Whiting
Hello PHP'ers! Just thought I would introduce myself to the mailing list since I've worked with PHP for almost 10 years now and yet haven't really been community active ... I've developed quite a few open-source projects over the years that I hope someone here will find as useful as I have ... th

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Lester Caine
Richard Quadling wrote: My heads trying to remember something I may or may not have known to start with. If I hold datetimes in a DB in UTC and can represent a date to a user based upon a user preference Timezone (not an offset, but a real timezone : Europe/Berlin, etc.) am I missing anything?

Re: [PHP] Holding "datetimes" in a DB.

2013-03-01 Thread Simon Schick
Hi, Richard I, too, tought about switching to UTC times in my database. The only reason for me was to get prepared for globalisation. A good article about this consideration is written at PHP Gangsta (sorry, German only): http://www.phpgangsta.de/die-lieben-zeitzonen The reason, why I did not sw

Re: [PHP] webDAV/CalDAV client class experience ?

2013-03-01 Thread Adam Tauno Williams
On Mon, 2013-02-18 at 12:19 +0100, B. Aerts wrote: > >> - Adding the HTTP header "Accept: */*" made sure all read actions ( e.g. > >> GET, PROPFIND, REPORT) worked perfectly > > > > This is interesting. The Accept header has to do with what media types > > the browser will accept in return. I didn'

Re: [PHP] webDAV/CalDAV client class experience ?

2013-03-01 Thread Adam Tauno Williams
On Sun, 2013-02-17 at 21:26 -0600, tamouse mailing lists wrote: > On Sat, Feb 16, 2013 at 2:30 PM, B. Aerts wrote: > > - the biggest mistake: apparently I commented the fwrite() call to the > > stream, which explains why he went in time-out ... (in this case, please DO > > shoot the pianist) > Nah