This project is archived and is in readonly mode.
rake db:test:clone_structure fails when using Oracle adapter and :sql schema_format
Reported by Emrys Ingersoll | August 9th, 2008 @ 01:39 AM | in 3.x
Executing the db:test:clone_structure Rake task when using the 'oracle' adapter and the SQL schema format fails with an Oracle error similar to
OCIError: ORA-00911: invalid character: INSERT INTO schema_migrations (version) VALUES ('2');
which is caused by the ";" at the end of the statement.
I've included a patch that solves the issue.
Comments and changes to this ticket
-
bshand September 19th, 2008 @ 12:44 PM
- Tag changed from “patch, railties, rake” to “patch, railties, rake”
I had the same problem, using Rails 2.1.0 and Oracle 10g -- which was preventing me from running "rake test:units" successfully.
The above patch fixed the problem for me.
-
Pratik December 20th, 2008 @ 04:57 PM
- Assigned user set to “Pratik”
- State changed from “new” to “incomplete”
None in the core team uses Oracle, so sadly we have no way of verifying the patch. I'll apply the patch if we can get a few more +1s from people actually using Oracle, or even those maintaining Oracle adapter. Please make sure the backwards compatibility is maintained.
Thanks.
-
Emrys Ingersoll December 22nd, 2008 @ 10:10 PM
Not sure if this would be considered sufficient verification, but the oracle-enhanced adapter included this patch in 1.1.8.
-
Emrys Ingersoll December 22nd, 2008 @ 10:11 PM
Sorry, posted the same link twice =( I meant to post a link to the github commit:
-
-
bshand November 18th, 2009 @ 10:20 AM
This bug still affects Rails 2.2 and 2.3 (tested versions 2.2.3, 2.3.2 and 2.3.4) with Oracle 10g, and the same patch still works.
-
-
-
Santiago Pastorino February 2nd, 2011 @ 05:05 PM
- State changed from “incomplete” to “open”
- Importance changed from “” to “”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 05:05 PM
- State changed from “open” to “stale”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
bshand
Pratik