Monday, August 12, 2019, 1:06:00 PM, Gabor Grothendieck
<ggrothendi...@gmail.com> wrote:
> The whole point of this is to make it as easy as possible for the user.
> With other backends the database handles the types but with sqlite
> the user has to get involved.
> ...
> sqldf("select d as d__Date, d + 1 as nextDay__Date from DF", method
> = "name__class")
> ## d nextDay
> ## 1 2000-01-01 2000-01-02
NOTE: I don't know R, so I may be talking rubbish...
I *think* the idea of whoever suggested it was not that the *user*
should have to do things like the above, but that the INTERFACE
between R and SQLite should do it. In my simplistic view the interface
"knows" the input is a date ("as.Date(..)") and so would tack the
"...__date" hint on to the column name when talking to SQLite. Coming
back out of SQLite, the interface would recognize the "...__date" and
turn the value into an R date.
Graham Holden
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
