# Title avoiding spurious response **URL:** \ **Category:** Ruby\ **Created:** [July 5, 2008, 11:25am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258 "2008-07-05T11:25:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 5, 2008, 11:25am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/1 "2008-07-05T11:25:28Z")
for each db.execute row, i get a spurious respense like : sql = SELECT DISTINCT \* FROM moz\_bookmarks WHERE title LIKE ‘%\U%’; block\_given? = true bind\_vars.empty? = true db = #SQLite3::Database:0x4e5b9c, db.type\_translation() = false, stmt = #SQLite3::Statement:0x4db1c4 check( 101 ) -\> message: /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/results et.rb:69:in `commence’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/results et.rb:62:in `initialize’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/stateme nt.rb:164:in `new’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/stateme nt.rb:164:in `execute’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/databas e.rb:238:in `execute2’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/databas e.rb:189:in `prepare’ /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/databas e.rb:237:in `execute2’ /Users/yt/work/Ruby/SQL/MySQL/bookmarks\_from\_sqlite/moz\_bookmarks\_update \_backslash\_U.rb:16@eof = true, found = false, (@eof || found) = true even if there is no error. how to avoid that ? ---
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 5, 2008, 11:35am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/2 "2008-07-05T11:35:26Z")
Une Bévue [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/results > > even if there is no error. > > how to avoid that ? sorry i forgot to mention the root subject )) ---
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 5, 2008, 9:05pm UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/3 "2008-07-05T21:05:38Z")
On Sat, Jul 05, 2008 at 06:31:40PM +0900, Une B?vue wrote: > > et.rb:69:in `commence’ > > /opt/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.1/lib/sqlite3/databas > > > > even if there is no error. > > > > how to avoid that ? > > sorry i forgot to mention the root subject )) try this from the sqlite3 command line and see what you get: select id, typeof( title ), typeof( guid ) from moz\_bookmarks; That will tell you the internal sqlite storage type of the field you are requesting. I’m assuming the problem is with one of those fields, so try typeof() on any field that you want to test out. enjoy, -jeremy ---
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 6, 2008, 8:01am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/4 "2008-07-06T08:01:16Z")
Jeremy H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > try this from the sqlite3 command line and see what you get: > > select id, typeof( title ), typeof( guid ) from moz\_bookmarks; > > That will tell you the internal sqlite storage type of the field you are > requesting. I’m assuming the problem is with one of those fields, so try > typeof() on any field that you want to test out. id INTEGER PRIMARY KEY → integer type INTEGER → integer fk INTEGER → integer | null parent INTEGER → integer position INTEGER → integer title LONGVARCHAR → text | null keyword\_id INTEGER → integer | null folder\_type TEXT → text | null dateAdded INTEGER → integer lastModified INTEGER → integer I would suspect “LONGVARCHAR” ??? ---
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 6, 2008, 8:26am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/5 "2008-07-06T08:26:25Z")
On Sun, Jul 06, 2008 at 02:56:43PM +0900, Une B?vue wrote: > id INTEGER PRIMARY KEY -\> integer > > I would suspect “LONGVARCHAR” ??? Possibly, but I wouldn’t be for sure. In the other thread it looks like you have worked around it, so I guess that will work for you. enjoy, -jeremy ---
**Author:** ![Une\_BSSSSvS\_ue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/2acd7d/32.png) [@Une\_BSSSSvS\_ue](https://www.ruby-forum.com/u/Une_BSSSSvS_ue)\ **Post date:** [July 6, 2008, 11:06am UTC](https://www.ruby-forum.com/t/title-avoiding-spurious-response/142258/6 "2008-07-06T11:06:02Z")
Jeremy H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Possibly, but I wouldn’t be for sure. In the other thread it looks like you > have worked around it, so I guess that will work for you. using amalgalite, yes no prob with spurious response. but, afaik, amalgalite uses it’s own sqlite3 embeded (thru amalgamation). then afterall, i suspected myself 😉 i’ve re-installed sqlite3-ruby by gem : ~/gems%\> sudo gem install --remote sqlite3-ruby – –with-sqlite3-include=/opt/local/include –with-sqlite3-lib=/opt/local/lib Password: Building native extensions. This could take a while… Successfully installed sqlite3-ruby-1.2.2 1 gem installed Installing ri documentation for sqlite3-ruby-1.2.2… Installing RDoc documentation for sqlite3-ruby-1.2.2… ~/gems%\> no more spurious messages… sorry for the noise !