heres a special valentine to instiki users http://i86.photobucket.com/albums/k110/OwenJ1971/datingadweb.jpg
the one on the left is me On Thu, Feb 14, 2008 at 8:17 PM, Kris Weston <[EMAIL PROTECTED]> wrote: > wow what kind of person tries to sensibly answer the first post after i > get pissed off with you and flame you ? > wow he must be an amazing dude that dude. > > anyway im not really sorry for calling you names > but i accept that i have stopped now for five minutes > > John Van Voorbis you rock - are you dutch ? cos if you are that means > there are two nice uns... > > > On Thu, Feb 14, 2008 at 8:15 PM, Kris Weston <[EMAIL PROTECTED]> > wrote: > > > ah nice one - THANKS!!! > > its not Solaris - its NetBSD.. > > is Solaris useful for anything other than if you want to spend time > > watching something load ? > > once we have plundered zfs off it - we're home free no? > > > > i thought the rake migrate thing was for mysql.... > > if i ever get that piece of shit working i might write a how to cos it > > has caused me nuff pain... > > > > why the fuck did you answer that!??? > > > > anyway mucho thanks brother > > > > > > On Thu, Feb 14, 2008 at 8:09 PM, John Van Voorhis <[EMAIL PROTECTED]> > > wrote: > > > > > Disclaimer: It's been a long time since I worked with Solaris, and I > > > am not > > > a Ruby/Rails expert by any means. > > > > > > > > > > SystemStackError: stack level too deep: SELECT * FROM webs WHERE > > > (webs."id" > > > > = 1) > > > > > > > > ulimit -s says: > > > > stack limit > > > > 2048 > > > > > > > > should i change that ? > > > > > > Probably not. A simple SQL call should not run you out of stack space > > > (2MB > > > here). Check if there are any records in the 'webs' table at all. You > > > might > > > need to run the 'rake migrate database' command that does the initial > > > database populating. Though I would have thought that SQLite would > > > just > > > return an error if the webs table didn't exist. It could be that the > > > calling code is mishandling the error. > > > > > > > Building native extensions. This could take a while... > > > > ERROR: Error installing sqlite3-ruby: > > > > ERROR: Failed to build gem native extension. > > > > > > > > /usr/pkg/bin/ruby18 extconf.rb install sqlite3-ruby > > > > checking for sqlite3.h... no > > > > > > > > make > > > > make: don't know how to make ruby.h. Stop > > > > > > > > make: stopped in /usr/pkg/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1 > > > > /ext/sqlite3_api > > > > > > > > > > > > Gem files will remain installed in > > > /usr/pkg/lib/ruby/gems/1.8/gems/sqlite3- > > > > ruby-1.2.1 for inspection. > > > > Results logged to /usr/pkg/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1 > > > > /ext > > > > > > It looks like SQLlite3 is either not installed or not in your include > > > path > > > so the install of sqlite-rbuy failed. > > > > > > > test_create_system_form_displayed(AdminControllerTest): > > > > ActiveRecord::StatementInvalid: SQLite3::SQLException: no such > > > table: > > > > wiki_references: DELETE FROM wiki_references WHERE 1=1 > > > > > > This seems to mean that SQLite is installed and running but that the > > > database didn't get set up correctly. So my guess is that you need to > > > do > > > the rake migrate thing to set up the database. > > > > > > > > > As a final note, it really helps if your comments are clearly > > > separated from > > > your error listings. And as I keep telling my 5 year old, calling > > > names and > > > kicking the person you want to have help you is never a good idea. > > > > > > -- > > > John Van Voorhis > > > > > > > > > _______________________________________________ > > > Instiki-users mailing list > > > [email protected] > > > http://rubyforge.org/mailman/listinfo/instiki-users > > > > > > > >
_______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
