Jeremy-
Thanks for all the help. I added to the cspecify for that one test. But, now I'm having a really really bad thing happening when I run a lot of tests: Sequel::DatabaseError: Sequel::SqlAnywhere::SQLAnywhereException: Resource governor for 'prepared statements' exceeded This means that something is not being closed//cleaned-up properly. See this in Java if a statement is not closed. Looking at my code I don't see where I am not closing/freeing and comparing that to the AR code, I think I'm good. So, I think this is maybe a problem with the ruby sqlanywhere native driver. I updated the gist https://gist.github.com/gditrick/6240781 with the latest. From the ruby sqlanywhere native driver, it says to do sqlany_free_stmt(rs) on the result set statement. If you look at my code, I'm doing that after the yield on both my execute and execute_dui. So, unless Sequel is doing something behind the scenes, it has to be something with the sqlanywhere native driver. I may have to ping the developer of it, but AR is doing it the in a similar way. Very lost, -GregD ----- Original Message ----- From: "Jeremy Evans" <[email protected]> To: [email protected] Sent: Friday, August 16, 2013 6:07:08 PM Subject: Re: SqlAnywhere adapter Simple dataset operations with nasty table names should work correctly On Friday, August 16, 2013 1:16:18 PM UTC-7, GregD wrote: Anyone/Jeremy- I'm stomped on this one. Looks like I have to set up some sort of escaping expression someplace. Is there an example? I tried it in sybase dbisql client. Not able to create a table with those in their client. rspec ./spec/integration/spec_helper.rb:77 # Simple dataset operations with nasty table names should work correctly # SEQUEL_INTEGRATION_URL="sqlanywhere://localhost?DBN=Test;UID=dba;PWD=sql" rspec spec/integration/dataset_test.rb:244 Run options: include {:locations=>{"./spec/integration/dataset_test.rb"=>[244]}} "SELECT TOP 1 NULL AS \"NIL\" FROM \"I`T' [E]\"\"M\\S\"" "CREATE TABLE \"I`T' [E]\"\"M\\S\" (\"ID\" integer PRIMARY KEY IDENTITY, \"NUMBER\" integer)" What is the table name suppose to be? I tried escaping in dbisql with backslash, but could not get it to work. Sybase may not be able to do so? This spec is skipped for Microsoft SQL Server and Oracle because those databases are not not capable of escaping it. Most likely the same is true for Sybase. The specifications that use cspecify (short for "checked specify") are skipped on the given database types or adapter schemes. If you are aiming at getting a clean test run, you'll have to modify the specs to skip tests that the adapter/database is not capable of passing. 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 . -- 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.
