Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-15 Thread Jeremy Evans
On Wednesday, January 15, 2020 at 1:14:50 AM UTC-8, Bernhard Weichel wrote: > > in https://github.com/oneclick/rubyinstaller2/issues/108 I found a > solution by using another ADO provider. > > replace > >provider = "Microsoft.Jet.OLEDB.4.0" > > with > > provider =

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-15 Thread 'Bernhard Weichel' via sequel-talk
Am Mittwoch, 15. Januar 2020 01:37:21 UTC+1 schrieb Jeremy Evans: > > 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

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-14 Thread Jeremy Evans
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 > >

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-14 Thread 'Bernhard Weichel' via sequel-talk
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 ---

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread Jeremy Evans
On Sunday, January 12, 2020 at 1:53:23 PM UTC-8, Bernhard Weichel wrote: > > for your info, I tried to debug the line in question. rec[:"Nr"] yields a > numerical value. But i have the impression that the where clause only works > with strings, but not with numericals or booleans. > Incorrect,

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread 'Bernhard Weichel' via sequel-talk
for your info, I tried to debug the line in question. rec[:"Nr"] yields a numerical value. But i have the impression that the where clause only works with strings, but not with numericals or booleans. From: P:/OptigemBridge/obdev/03_OptigemBridge/10_Sources/mediator_og_vr.rb @ line 133 :

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread 'Bernhard Weichel' via sequel-talk
Am Sonntag, 12. Januar 2020 20:43:51 UTC+1 schrieb Jeremy Evans: > > On Sunday, January 12, 2020 at 2:25:10 AM UTC-8, Bernhard Weichel wrote: >> >> Hi >> >> I have an application running with ruby 1.93 and sequel 4.18.0. I have >> statements like >> >>

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread Jeremy Evans
On Sunday, January 12, 2020 at 2:25:10 AM UTC-8, Bernhard Weichel wrote: > > Hi > > I have an application running with ruby 1.93 and sequel 4.18.0. I have > statements like > > ogdb.projectcategorys.where('Zuordnungssperre = FALSE') > > No we want to upgrade the application to Ruby 2.6 and squel

Re: How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread 'Bernhard Weichel' via sequel-talk
It appeare to me that there are more incompatibilites between sequel 4.18 and 5.28 with respect to JET database engeine. I tried to overcome the problems before but then I get further internal errors P:/OptigemBridge/tools_26/Ruby26-x86/lib/ruby/gems/2.6.0/gems/sequel-5.28.0/lib/s

How to handle boolean in literal where clauses with squel 5.28

2020-01-12 Thread 'Bernhard Weichel' via sequel-talk
Hi I have an application running with ruby 1.93 and sequel 4.18.0. I have statements like ogdb.projectcategorys.where('Zuordnungssperre = FALSE') No we want to upgrade the application to Ruby 2.6 and squel 5.28 the statement now throws: Sequel::Error: Invalid filter expression: