On 14 Feb 2011, at 08:14, craayzie wrote:
So weird. I run the migration but it does nothing to db/schema.rb:
add_index snippets, [name, site_id], :name =
index_snippets_on_name_and_site_id, :unique = true
add_index snippets, [name], :name = name, :unique = true
Here's the exact
Snippet:
name:
message:
'Name wurde schon verwendet'
scope:
site_id
in config/vhost.yml
should do the trick ...
On 14.02.2011, at 09:14, craayzie wrote:
So weird. I run the migration but it does nothing to db/schema.rb:
add_index snippets, [name,
Hi all,
Is anyone working on getting the new html5 input types (such as email, url,
etc) and attributes (such as required) into the html5 forms extension? I didn't
notice it working and was thinking about tackling it.
B
Bernard Yu
Content Strategist, UX Advocate,
HTML Junkie
enguindesign.com
What is it about the config/vhost.yml file that would make this unique
index on the name attribute go away?
On a related note it looks like sqlite requires that all indexed
columns be unique!
SQLite3::ConstraintException: indexed columns are not unique: CREATE
UNIQUE INDEX name ON snippets (name)
The migration to remove the unique constraint works great (below) but
when I try to roll it back I get the following from sqlite:
$ rake db:rollback
(in /Users/username/Sites/heroku)
== CleanUpSnippetConstraints1: reverting
=
-- remove_index(:snippets,
Below is the migration that finally did the trick! There wasn't really
a need to have an index on the name attribute anyways since it'll
always require the site_id.
I'm still interested in Haselwanter's note about how the config/
vhost.yml file alone should have taken care of this. Am I missing
you should be able to create a setting like `kramdown.coderay_line_numbers =
false` or possibly `... = :false` - to see all the available options check
out lib/kramdown_filter.rb.
