> On 18 Sep 2013, at 00:57, Robb Shecter wrote:
>
> Matt jones wrote:
>>
>> The best type to use to store DateTime objects is database-dependent:
>
> So Ketan's finding seems to be correct, and this is something we should fix.
> I.e., Rails' concept of timestamps should be database independen
On Sep 17, 2013, at 6:57 PM, Robb Shecter wrote:
> Matt jones wrote:
>
> The best type to use to store DateTime objects is database-dependent:
>
>
> So Ketan's finding seems to be correct, and this is something we should fix.
> I.e., Rails' concept of timestamps should be database independen
Matt jones wrote:
>
> The best type to use to store DateTime objects is database-dependent:
>
>
So Ketan's finding seems to be correct, and this is something we should
fix. I.e., Rails' concept of timestamps should be database independent,
just as its concept of the primary key type is. (?)
-
On Sep 11, 2013, at 10:33 PM, Ketan Padegaonkar wrote:
> Hi,
>
> I noticed that datetimes and timestamps are handled inconsistently between
> databases. Mysql treats them as datetime[1]. Postgres treats them as
> timestamp[2]. Sqlite treats them as datetime[3].
>
> I read through the document
Hi,
I noticed that datetimes and timestamps are handled inconsistently between
databases. Mysql treats them as datetime[1]. Postgres treats them as
timestamp[2]. Sqlite treats them as datetime[3].
I read through the documentation around specifics of datetime and
timestamps in various databases an
