I've not seen anything like this with rails 2.3.2 and edge hobo. Might it be something they tweaked with 2.3.4?
Though I guess, either way, it needs to be fixed. On Sep 20, 10:40 am, Marcel Waldvogel <[email protected]> wrote: > I have been following Hobo for quite some time now and wanted to > actually use it in a project of mine, as it by far seems to be the > best toolkit around for my purpose. Unfortunately, there seem to be > problems with handling time (and time zone). > > Do the following: > % hobo test > % cd test > % history > % ./script/generate hobo_model_resource sometime snapshot:timestamp > % ./script/generate hobo_migration > ["m" Return Return] > % ./script/server > > Then switch to your browser, point it to your Hobo URL, create a user > and start creating a "Sometimes" object. Note the time you entered > before you save it. Notice that the displayed time is modified by your > timezone offset when it is displayed. Edit it, save, and it is now > twice the TZ offset away from the time you originally entered. > > This is obviously absolutely unusable when the database should contain > time information besides created_at and updated_at. > > I would be glad if you could tell me where I should look for further > advice (I have been trying several of the Rails suggestions, but to no > avail). My configuration: The latest Gems (Rails 2.3.4, Hobo 0.8.8) > > Thanks! > -Marcel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
