From: fistfvck <fistfvck@...>
Date: 2010-06-24T10:11:10+09:00
Subject: Re: SQLite placeholder problem

hi.

see blow.
sqlite3-ruby-1.3.0/lib/sqlite3/database.rb:119
          warn(<<-eowarn) if $VERBOSE
  #{caller[0]} is calling SQLite3::Database#execute with nil or
multiple bind params
  without using an array.  Please switch to passing bind parameters as an array.
          eowarn

so, change like this:
listing20.rb:33
  $db.execute("INSERT INTO people (name, job, gender, age) VALUES (?,
?, ?, ?)", [name, job, gender, age])

listing20.rb:40
  person = $db.execute("SELECT * FROM people WHERE name = ? OR id =
?", [id, id.to_i]).first

Regards
2010/6/24 Yuriy Skobov <yuriyskobov@hotmail.com>:
> Waldemar Dick wrote:
>> Windows XP with:
>> - sqlite3 3.6.10
>> - gem sqlite3-ruby-1.2.5
>> - ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-cygwin]
>
> Found it.  It was the gem sqlite3-ruby-1.3.0 that was causing this.
> With version 1.2.5, it works like it's supposed to.
> --
> Posted via http://www.ruby-forum.com/.
>
>