This has been happening to me while I have been making my extension,
It worked once... after that the schema didn't get updated. I am also
getting errors regarding the unique config key on MySQL but again, it
worked...once.
So far I have been unable to replicate both situations, I am still
trying to figure out what is goig on..
Jeff
N. Turnage wrote:
Jim Gay wrote:
Radiant should update the schema.rb file
But it doesn't. This is the content of my schema.rb file:
...
# This file is auto-generated from the current state of the database.
Instead of editing this file,
# please use the migrations feature of ActiveRecord to incrementally
modify your database, and
# then regenerate this schema definition.
#
# Note that this schema.rb definition is the authoritative source for
your database schema. If you need
# to create the application database on another system, you should be
using db:schema:load, not running
# all the migrations from scratch. The latter is a flawed and
unsustainable approach (the more migrations
# you'll amass, the slower it'll run and the greater likelihood for
issues).
#
# It's strongly recommended to check this file into your version
control system.
ActiveRecord::Schema.define(:version => 0) do
end
...
The file is auto-generated, so how do I get a look at the current
state of affairs?
~Nate
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant