postgresql 8.3 doesn't like single quoted role names in the OWNER clause
Reported by azimux | August 7th, 2008 @ 11:41 AM | in 2.1.1
postgresql does not like single quoted role names for the OWNER clause
This bug prevents me from being able to create the test database successfully when doing rake test. To reproduce this simply try running rake test on any rails app while using postgresql. It might require a recent version to expose the bug. I am running 8.3.3
The fix is trivial, unquoting the ownername, but I've attatched a patch anyways
Comments and changes to this ticket
-
isak August 8th, 2008 @ 10:07 AM
- → Tag changed from “activerecord bug edge patch postgresql” to “2.1 activerecord bug edge patch postgresql tiny”
The bug applies to 8.2 as well, probably earlier versions too.
Adding "tiny" and "2.1" tags.
-
Pratik August 22nd, 2008 @ 04:25 AM
- → Assigned user changed from “” to “Tarmo Tänav”
-
Jeremy Kemper August 22nd, 2008 @ 05:33 AM
- → Milestone changed from “2.x” to “2.1.1”
- → State changed from “new” to “open”
-
Tarmo Tänav August 22nd, 2008 @ 07:59 AM
- no changes were found...
-
Tarmo Tänav August 22nd, 2008 @ 07:59 AM
Actually the values should be quoted, but with double-quotes because they are database name references and not values.
-
-
Repository August 22nd, 2008 @ 08:58 AM
- → State changed from “open” to “resolved”
(from [d3b894563a114912113b816f07ed16511363fb65]) Properly quote CREATE DATABASE parameters in postgresql [#771 state:resolved] http://github.com/rails/rails/co...
-
Repository August 25th, 2008 @ 09:31 AM
(from [a6619865d0191c1001d1f25e8f4d111a0e9f78d2]) Properly quote CREATE DATABASE parameters in postgresql [#771 state:resolved] http://github.com/rails/rails/co...
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
