On Jul 2, 2:01 pm, Scott LaBounty <[email protected]> wrote: > Jeremy, > > That would be my guess too (string format issue). I'm just doing this for > learning / teaching purposes, so I can certainly work around it. > > I think what I missed earlier is that sqlite actually stores a Date as a > string (true?) and so I'll have to convert to match. In a "real" database > (mySQL, etc.), passing the ruby Date class should work. Is that correct?
SQLite stores almost all columns as strings (everything except integer primary keys). Almost all other databases have native date types. You can use Date objects with SQLite and Sequel, you just have to be consistent about always using Date objects. You can't use Date objects in one place and strings in another place (unless the string is in the exact same format Sequel uses for the Date object). Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
