On Tuesday, January 14, 2020 at 2:42:30 PM UTC-8, Bernhard Weichel wrote:
>
> Jeremy, thanks for your response.
>
> I created a minimal self-contained example in the attached file.
> I do not manage to perform
>
> it does work with ruby 1.9.3, having sequel 4.49 where it produces
>
> P:\OptigemBridge\obdev\80_sequel-tests>ruby testwithmdb.rb
> all data unfiltered
> -------------------
> {:ID=>6, :Numerical=>1, :Boolean=>true, :Text=>"\"Record 1 boolean
> true\""}
> {:ID=>7, :Numerical=>2, :Boolean=>false, :Text=>"\"Record 2 boolean
> false\""}
>
> playing with boolean
> --------------------
>
> table.where(Boolean: true) -> SELECT * FROM [Optigem] WHERE ([Boolean] =
> -1)
> {:ID=>6, :Numerical=>1, :Boolean=>true, :Text=>"\"Record 1 boolean
> true\""}
>
> P:\OptigemBridge\obdev\80_sequel-tests>gem which sequel
>
> P:/OptigemBridge/tools/ruby/lib/ruby/gems/1.9.1/gems/sequel-4.49.0/lib/sequel.rb
>
> sorry I do not manage to run it as bundle exec ruby testwithmdb.rb
>
> but with ruby 2.6 I get
>
> P:\OptigemBridge\obdev\80_sequel-tests>bundle exec ruby testwithmdb.rb
> all data unfiltered
> -------------------
> {:ID=>6, :Numerical=>1, :Boolean=>true, :Text=>"\"Record 1 boolean
> true\""}
> {:ID=>7, :Numerical=>2, :Boolean=>false, :Text=>"\"Record 2 boolean
> false\""}
>
> playing with boolean
> --------------------
>
> table.where(Boolean: true) -> SELECT * FROM [Optigem] WHERE ([Boolean] =
> -1)
> WIN32OLERuntimeError: (in OLE method `Execute': )
> OLE error code:80040E14 in Microsoft JET Database Engine
> Interner Fehler bei OLE-Automatisierung
> HRESULT error code:0x80020009
> Ausnahmefehler aufgetreten.
>
> From: P:/OptigemBridge/obdev/80_sequel-tests/testwithmdb.rb @ line 34 :
>
> 29: puts
> 30: puts "table.where(Boolean: true) -> #{boolean.sql}"
> 31: puts boolean.all
> 32: rescue Exception => e
> 33: puts e
> => 34: require 'pry';binding.pry
> 35: end
> [1] pry(main)>
>
>
> could it be that ruby 1.9.3 is 32 bit while 2.6.0 is 64 bit? But then it
> should not handle select statements without the where clause either.
>
Could be, it's hard to say. It does appear to be an issue with Ruby and
not a Sequel-specific issue, though.
Thanks,
Jeremy
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/sequel-talk/a6558866-c156-4683-bfa6-d9cb30ed3c97%40googlegroups.com.
