On Wed, Dec 2, 2009 at 5:07 AM, Eric Allen <[email protected]> wrote:
> I wonder if you could use SQLite's .dump command to save the data, blow away
> the database and create one with the right schema using rake, then re-import
> the data into SQLite. You might need to manually translate the 1/0's to
> t/f's, but once you're in a text file it shouldn't be too bad. Obviously
> keep copious backups...
Yeah, I started that process last night.
One thing I noticed while doing that- the 'tracks-17-blank.db' in your
branch is not actually, you know, 'blank' :) It looks like it contains
a bunch of Henrik's stuff- his user account, five todos ('learn
ruby'), etc. Might want to revert that to a truly blank db before
merging to bsag's trunk.
Thanks-
Luis
> On Dec 2, 2009, at 2:51 AM, Luis Villa wrote:
>
> On Tue, Dec 1, 2009 at 8:42 PM, Eric Allen <[email protected]> wrote:
>
> Hmm. I can't seem to replicate it here. Could it be some kind of caching
>
> bug? What about trying a different browser or re-starting your browser? Do
>
> you have a caching reverse proxy in front of the Tracks server?
>
> No, no proxies involved; seeing it with both ffox and chrome.
>
> After further poking, this is my db's fault- it is related to this thread:
> http://www.mail-archive.com/[email protected]/msg00747.html
>
> The schema should indicate that the field is a boolean but instead it
> is an integer and so new contexts default to 1 rather than t. Not sure
> how to fix the schema, but I suppose a bit more time with google will
> resolve that. Sorry to have wasted your time, Eric.
>
> Luis
>
> On Dec 1, 2009, at 2:00 PM, Luis Villa wrote:
>
> Hey, all-
>
> I just created a new account for my wife, and the first thing we did
>
> was create some contexts using the organize->contexts page (aka
>
> $SERVER/contexts/). Here is a step-by-step process, with the weird
>
> outcome:
>
> 1) go to /contexts/
>
> 2) type context name 'A', click 'add context'
>
> 3) observe that there is now a context name 'A' listed under 'Active
>
> Contexts'; in sqlite3 observe that
>
> sqlite> select * from contexts where name='A';
>
> 37|A|8|0|3|2009-12-01 18:43:16|2009-12-01 18:43:16
>
> 4) click on context A, to go to $SERVER/contexts/37
>
> 5) enter 'B' as a description; hit 'Add Action'
>
> 6) observe that there is now an action 'B' visible in the web UI and
>
> in sqlite3 observe that
>
> sqlite> select * from todos where description='B';
>
> 1664|37||B||2009-12-01 18:45:32|||3||active||2009-12-01 18:45:32
>
> So here is where it starts getting weird.
>
> 7) click 'home'. should be a context A and a todo in it, B. No context
>
> and no todo.
>
> 8) click 'organize->contexts'. should be a context A, like there was
>
> in step 3, but voila, it too is gone. Still there in the DB, and if I
>
> go directly to /contexts/37 still there as well, but just not showing
>
> up in the UI.
>
> Weird, huh?
>
> Software-wise, this is with latest git (off epall's branch) and having
>
> run rake db:migrate after the last git pull.
>
> I'm very, very rusty at debugging rails, and never debugged rails and
>
> sqlite, so if anyone has any pointers, I'm all ears.
>
> Note that this is with the same rusty old sqlite3 db that I once
>
> (poorly?) imported from a mysql install, so it is possible that
>
> funkiness lurks in there. I'd be happy to export everything and
>
> re-import it cleanly if such a thing were possible, and test again
>
> then, but AFAICT it isn't possible. :/
>
> Thanks for any suggestions-
>
> Luis
>
> _______________________________________________
>
> Tracks-discuss mailing list
>
> [email protected]
>
> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
>
>
>
>
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
