On Friday, October 11, 2013 4:37:08 AM UTC-7, GregD wrote:
>
>
> On Oct 10, 2013, at 8:17 PM, Jeremy Evans <[email protected]<javascript:>>
> wrote:
>
>
>> For what it is worth, I created a gist for helping with this. It was
>> hard to remember what exactly I did setting up sqlanywhere on my ubuntu VM.
>>
>>
>> https://gist.github.com/gditrick/6890699
>>
>
> This gist was very helpful. I got a Linux VM setup with SQLAnywhere 16
> Developer.
>
>
> Good. I didn't know if that would help or not since I was going off
> memory and had done it months ago.
>
> 16? I guess, the Developer is on a different release numbering system.
> The latest commercial I have is 12.0.1 build 3967.
>
>
> On ruby 2.0.0, I'm getting:
>
> 1) Database schema parser should parse current date defaults from the
> schema properly
> Failure/Error: Unable to find matching line from backtrace
> expected: #<Sequel::SQL::Constant @constant=>:CURRENT_DATE>
> got: nil (using ==)
> # ./spec/integration/schema_test.rb:114:in `block (2 levels) in <top
> (required)>'
>
> Finished in 36.45 seconds
> 541 examples, 1 failure, 3 pending
>
> On ruby 1.8.7, I'm getting:
>
> 542 examples, 26 failures, 3 pending
>
> Most of the failures appear to be order related. Without looking at the
> code, I'm guessing it's due to relying on hash order.
>
> Haven't tried the jruby/sqlanywhere adapter yet.
>
> Anyway, now that I have a test environment setup, I should be able to work
> through these issues.
>
>
> Sorry I made more work for you. I only ran them through 1.9.3 and jruby
> 1.7.4 or 5. I can take a look especially at the 2.0.0 problem this weekend
> if you want me to. That 1 looks bad and has me baffled. I don't have a
> 1.8.7 env setup. Did it run thru 1.9.3 okay?
>
With a small change to the adapter so it doesn't depend on hash order, I'm
was getting the same results on 1.8.7 as on 2.0.0:
Failures:
1) Database schema parser should parse current date defaults from the
schema properly
Failure/Error: Unable to find matching line from backtrace
expected: #<Sequel::SQL::Constant @constant=>:CURRENT_DATE>
got: nil (using ==)
# ./spec/integration/schema_test.rb:114
Finished in 1 minute 2.12 seconds
542 examples, 1 failure, 3 pending
This failure was due to a bug in the shared adapter, where it was trying to
set the :default value in the schema hash to an object, instead of letting
column_schema_to_ruby_default handle it. There was also a small patch
needed to the shared Database code to get it to recognize today() as a
current date.
With these changes, I got a clean spec run on 1.8.7, 1.9.3, and 2.0.0.
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/groups/opt_out.
