DATEIME's value is adjusted by an hour without consent

Hi All I'm experiencing a taxing problem I've not been able to find a solution to on google! I've got a table with some DATETIME columns present. Whenever I call save, the DATETIME column value gets put back by an hour. I'm guessing that torque is converting the value from UTC to GMT (or

DATEIME's value is adjusted by an hour without consent

Hi All I'm experiencing a taxing problem I've not been able to find a solution to on google! I've got a table with some DATETIME columns present. Whenever I call save, the DATETIME column value gets put back by an hour. I'm guessing that torque is converting the value from UTC to GMT (or

Re: DATEIME's value is adjusted by an hour without consent

Hi John, Sounds like a display problem. Have you compared the long time value just before save and on retrieval. I would check the locale settings for the client and server. Regards, Malcolm Kendall John Dunne wrote: Hi All I'm experiencing a taxing problem I've not been able to find a

Using multiple joins to a table

Hiho! I've little freaky question. There a two tables: Table #1 (debitor) has following columns: id (primary) address_id (not null, foreign key to address) invoice_address_id (not null, foreign key to address) delivery_address_id (not null, foreign key to address) ... Table #2