-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''d appreciate it if those who''ve upgraded from 0.13.1 to the 1.0 release candidate would offer suggestions to improve the manual: http://manuals.rubyonrails.org/read/chapter/121 What''s unclear, not covered, broken? Gotchas, tips? Many thanks, jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5 LvhioOxCDTVbZPRn0tn/dWk=5Awp -----END PGP SIGNATURE-----
A mention of the new Rakefile structure wouldn''t go astray (since switchtower doesn''t work until you update it)... plus the fact that you should probably re-run ''rails'' over your project directory to update all the core files... More as I think of them :) -DF On 11/1/05, Jeremy Kemper <jeremy-w7CzD/W5Ocjk1uMJSBkQmQ@public.gmane.org> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > I''d appreciate it if those who''ve upgraded from 0.13.1 to the 1.0 > release candidate would offer suggestions to improve the manual: > > http://manuals.rubyonrails.org/read/chapter/121 > > What''s unclear, not covered, broken? Gotchas, tips? > > Many thanks, > jeremy > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (Darwin) > > iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5 > LvhioOxCDTVbZPRn0tn/dWk> =5Awp > -----END PGP SIGNATURE----- > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Ohhhh wait.... You already mentioned that. Sorry :) Cheers, -DF On 11/1/05, David Felstead <david.felstead-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> A mention of the new Rakefile structure wouldn''t go astray (since > switchtower doesn''t work until you update it)... plus the fact that > you should probably re-run ''rails'' over your project directory to > update all the core files... > > More as I think of them :) > > -DF > > On 11/1/05, Jeremy Kemper <jeremy-w7CzD/W5Ocjk1uMJSBkQmQ@public.gmane.org> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi all, > > > > I''d appreciate it if those who''ve upgraded from 0.13.1 to the 1.0 > > release candidate would offer suggestions to improve the manual: > > > > http://manuals.rubyonrails.org/read/chapter/121 > > > > What''s unclear, not covered, broken? Gotchas, tips? > > > > Many thanks, > > jeremy > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2 (Darwin) > > > > iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5 > > LvhioOxCDTVbZPRn0tn/dWk> > =5Awp > > -----END PGP SIGNATURE----- > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 31, 2005, at 2:33 PM, David Felstead wrote:> Ohhhh wait.... You already mentioned that. Sorry :) > > Cheers, > > -DF > > On 11/1/05, David Felstead <david.felstead-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> A mention of the new Rakefile structure wouldn''t go astray (since >> switchtower doesn''t work until you update it)... plus the fact that >> you should probably re-run ''rails'' over your project directory to >> update all the core files... >> >> More as I think of them :) >> >> -DF >>I did mention it, but I think it should be clearer. The updated "Performing the Upgrade" chapter: http://manuals.rubyonrails.org/read/chapter/120 Thanks for the extra pair of eyes! jeremy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDZqp3AQHALep9HFYRAlMfAKCCiKMC5F3vOurYXnwhYPFIa8jXQwCgsMlt ILvW6nnoocTGCs3SkrtPRZI=j6jE -----END PGP SIGNATURE-----
Hi Jeremy,
Thanks for the link to the book.
I had a couple of issues when I upgraded:
1. the "/" route now fails - I get
"ActionController::RoutingError
(Recognition failed for "/"):" and also this error in the log:
Rendering
d:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.10.2/lib/action_controller/templates/rescues/layout.rhtml
(404 Pag
e Not Found)
I have tried both of the following in routes.rb to no avail:
map.connect ''/'', :controller =>
''stories'', :action => ''list'', :title
=> ''Welcome''
map.connect '''', :controller =>
''stories'', :action => ''list'', :title
=>
''Welcome''
the latter is the original one I had before the upgrade
2. some scriptalicious components that worked before now fail. I use
the following to delete items:
<%= link_to_remote "Remove",
:url=>{
:controller=>"records",
:action=>"destroy",
:id=>record.id},
:loading=>"status(''record#{record.id}'')",
:complete=>"new
Effect.Fade(''record#{record.id}'')"
%>
the delete still works, but there is no fade out.
Sorry if I''m missing obvious things here - but they are the two things
that have come up ...
Many thanks in advance.
CHEERS> SAM
Jeremy Kemper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> I''d appreciate it if those who''ve upgraded from 0.13.1 to
the 1.0
> release candidate would offer suggestions to improve the manual:
>
> http://manuals.rubyonrails.org/read/chapter/121
>
> What''s unclear, not covered, broken? Gotchas, tips?
>
> Many thanks,
> jeremy
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (Darwin)
>
> iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5
> LvhioOxCDTVbZPRn0tn/dWk> =5Awp
> -----END PGP SIGNATURE-----
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
Here''s another freaky issue that has arisen after the upgrade.
Running the following scaffold:
ruby script\generate scaffold History History
fails to produce any new code - I did have History files previously but
I deleted all of them - the output I currently get is:
D:\user\Code\ruby\prometheus>ruby script\generate scaffold History History
exists app/controllers/
exists app/helpers/
exists app/views/history
exists test/functional/
dependency model
exists app/models/
exists test/unit/
exists test/fixtures/
identical app/models/history.rb
identical test/unit/history_test.rb
identical test/fixtures/histories.yml
error Before updating scaffolding from new DB schema, try
creating a table for your model (History)
The files definitely do not exist. I''ve also tried destroying and
re-creating, but only some of the files get recreated:
D:\user\Code\ruby\prometheus>ruby script\destroy scaffold History History
rm public/stylesheets/scaffold.css
missing app/views/layouts/history.rhtml
missing app/helpers/history_helper.rb
missing test/functional/history_controller_test.rb
missing app/controllers/history_controller.rb
missing app/views/history/edit.rhtml
missing app/views/history/new.rhtml
missing app/views/history/show.rhtml
missing app/views/history/list.rhtml
dependency model
rm test/fixtures/histories.yml
rm test/unit/history_test.rb
rm app/models/history.rb
notempty test/fixtures
notempty test
notempty test/unit
notempty test
notempty app/models
notempty app
notempty test/functional
notempty test
rmdir app/views/history
notempty app/views
notempty app
notempty app/helpers
notempty app
notempty app/controllers
notempty app
D:\user\Code\ruby\prometheus>ruby script\generate scaffold History History
exists app/controllers/
exists app/helpers/
create app/views/history
exists test/functional/
dependency model
exists app/models/
exists test/unit/
exists test/fixtures/
create app/models/history.rb
create test/unit/history_test.rb
create test/fixtures/histories.yml
error Before updating scaffolding from new DB schema, try
creating a table for your model (History)
Any help greatly appreciated.
I see that there is no table in the DB schema but I am trying to make
something to map to a log table that conflicts with WebBrick - I have
also tried with other table existing classes but to no avail - seems
like the generate scaffold function is broken ...
CHEERS> SAM
Jeremy Kemper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> I''d appreciate it if those who''ve upgraded from 0.13.1 to
the 1.0
> release candidate would offer suggestions to improve the manual:
>
> http://manuals.rubyonrails.org/read/chapter/121
>
> What''s unclear, not covered, broken? Gotchas, tips?
>
> Many thanks,
> jeremy
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (Darwin)
>
> iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5
> LvhioOxCDTVbZPRn0tn/dWk> =5Awp
> -----END PGP SIGNATURE-----
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
Okay, so I worked around this, but it seems like 0.14.2 is kind of stricter than before, i.e. I must have a table of correct name in my db to run scaffold, and I must pass in both model and controller name at the command line - I thought that if they were the same I could just specify one before (maybe my imagination ...), but certainly I didn''t need a matching table name before. This new strictness is kind of irritating if I have to create dummy tables each time I want to deal with some legacy name collision, like the log table in our db and log in WebBrick. CHEERS> SAM Sam Joseph wrote:> Here''s another freaky issue that has arisen after the upgrade. > > Running the following scaffold: > > ruby script\generate scaffold History History > > fails to produce any new code - I did have History files previously > but I deleted all of them - the output I currently get is: > > D:\user\Code\ruby\prometheus>ruby script\generate scaffold History > History > exists app/controllers/ > exists app/helpers/ > exists app/views/history > exists test/functional/ > dependency model > exists app/models/ > exists test/unit/ > exists test/fixtures/ > identical app/models/history.rb > identical test/unit/history_test.rb > identical test/fixtures/histories.yml > error Before updating scaffolding from new DB schema, try > creating a table for your model (History) > > The files definitely do not exist. I''ve also tried destroying and > re-creating, but only some of the files get recreated: > > D:\user\Code\ruby\prometheus>ruby script\destroy scaffold History History > rm public/stylesheets/scaffold.css > missing app/views/layouts/history.rhtml > missing app/helpers/history_helper.rb > missing test/functional/history_controller_test.rb > missing app/controllers/history_controller.rb > missing app/views/history/edit.rhtml > missing app/views/history/new.rhtml > missing app/views/history/show.rhtml > missing app/views/history/list.rhtml > dependency model > rm test/fixtures/histories.yml > rm test/unit/history_test.rb > rm app/models/history.rb > notempty test/fixtures > notempty test > notempty test/unit > notempty test > notempty app/models > notempty app > notempty test/functional > notempty test > rmdir app/views/history > notempty app/views > notempty app > notempty app/helpers > notempty app > notempty app/controllers > notempty app > > D:\user\Code\ruby\prometheus>ruby script\generate scaffold History > History > exists app/controllers/ > exists app/helpers/ > create app/views/history > exists test/functional/ > dependency model > exists app/models/ > exists test/unit/ > exists test/fixtures/ > create app/models/history.rb > create test/unit/history_test.rb > create test/fixtures/histories.yml > error Before updating scaffolding from new DB schema, try > creating a table for your model (History) > > Any help greatly appreciated. > > I see that there is no table in the DB schema but I am trying to make > something to map to a log table that conflicts with WebBrick - I have > also tried with other table existing classes but to no avail - seems > like the generate scaffold function is broken ... > > CHEERS> SAM > > Jeremy Kemper wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I''d appreciate it if those who''ve upgraded from 0.13.1 to the 1.0 >> release candidate would offer suggestions to improve the manual: >> >> http://manuals.rubyonrails.org/read/chapter/121 >> >> What''s unclear, not covered, broken? Gotchas, tips? >> >> Many thanks, >> jeremy >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.2 (Darwin) >> >> iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5 >> LvhioOxCDTVbZPRn0tn/dWk>> =5Awp >> -----END PGP SIGNATURE----- >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > >
So a follow up here - despite now having scaffolded history the following:
class History < ActiveRecord::Base
set_table_name "log"
end
generates the following error:
undefined local variable or method `table_name'' for
#<History:0x33323c8>
and yet the exact same code works for other models ...
kudos if anyone can figure this out ....
CHEERS> SAM
Sam Joseph wrote:
> Okay, so I worked around this, but it seems like 0.14.2 is kind of
> stricter than before, i.e.
>
> I must have a table of correct name in my db to run scaffold, and I
> must pass in both model and controller name at the command line - I
> thought that if they were the same I could just specify one before
> (maybe my imagination ...), but certainly I didn''t need a matching
> table name before.
>
> This new strictness is kind of irritating if I have to create dummy
> tables each time I want to deal with some legacy name collision, like
> the log table in our db and log in WebBrick.
>
> CHEERS> SAM
>
> Sam Joseph wrote:
>
>> Here''s another freaky issue that has arisen after the upgrade.
>>
>> Running the following scaffold:
>>
>> ruby script\generate scaffold History History
>>
>> fails to produce any new code - I did have History files previously
>> but I deleted all of them - the output I currently get is:
>>
>> D:\user\Code\ruby\prometheus>ruby script\generate scaffold History
>> History
>> exists app/controllers/
>> exists app/helpers/
>> exists app/views/history
>> exists test/functional/
>> dependency model
>> exists app/models/
>> exists test/unit/
>> exists test/fixtures/
>> identical app/models/history.rb
>> identical test/unit/history_test.rb
>> identical test/fixtures/histories.yml
>> error Before updating scaffolding from new DB schema, try
>> creating a table for your model (History)
>>
>> The files definitely do not exist. I''ve also tried destroying
and
>> re-creating, but only some of the files get recreated:
>>
>> D:\user\Code\ruby\prometheus>ruby script\destroy scaffold History
>> History
>> rm public/stylesheets/scaffold.css
>> missing app/views/layouts/history.rhtml
>> missing app/helpers/history_helper.rb
>> missing test/functional/history_controller_test.rb
>> missing app/controllers/history_controller.rb
>> missing app/views/history/edit.rhtml
>> missing app/views/history/new.rhtml
>> missing app/views/history/show.rhtml
>> missing app/views/history/list.rhtml
>> dependency model
>> rm test/fixtures/histories.yml
>> rm test/unit/history_test.rb
>> rm app/models/history.rb
>> notempty test/fixtures
>> notempty test
>> notempty test/unit
>> notempty test
>> notempty app/models
>> notempty app
>> notempty test/functional
>> notempty test
>> rmdir app/views/history
>> notempty app/views
>> notempty app
>> notempty app/helpers
>> notempty app
>> notempty app/controllers
>> notempty app
>>
>> D:\user\Code\ruby\prometheus>ruby script\generate scaffold History
>> History
>> exists app/controllers/
>> exists app/helpers/
>> create app/views/history
>> exists test/functional/
>> dependency model
>> exists app/models/
>> exists test/unit/
>> exists test/fixtures/
>> create app/models/history.rb
>> create test/unit/history_test.rb
>> create test/fixtures/histories.yml
>> error Before updating scaffolding from new DB schema, try
>> creating a table for your model (History)
>>
>> Any help greatly appreciated.
>>
>> I see that there is no table in the DB schema but I am trying to make
>> something to map to a log table that conflicts with WebBrick - I
>> have also tried with other table existing classes but to no avail -
>> seems like the generate scaffold function is broken ...
>>
>> CHEERS> SAM
>>
>> Jeremy Kemper wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Hi all,
>>>
>>> I''d appreciate it if those who''ve upgraded from
0.13.1 to the 1.0
>>> release candidate would offer suggestions to improve the manual:
>>>
>>> http://manuals.rubyonrails.org/read/chapter/121
>>>
>>> What''s unclear, not covered, broken? Gotchas, tips?
>>>
>>> Many thanks,
>>> jeremy
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.2 (Darwin)
>>>
>>> iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5
>>> LvhioOxCDTVbZPRn0tn/dWk>>> =5Awp
>>> -----END PGP SIGNATURE-----
>>> _______________________________________________
>>> Rails mailing list
>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Rails mailing list
>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>
>>
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
Hi All and Jeremy in particular, So I managed to solve both these issues - both of them due to sloppiness on my part. 1. when copying over the new routes.rb file I ended up with nested "ActionController::Routing::Routes.draw do |map|" statements - interestingly the error generated sent me off looking at completely the wrong things - so this is just a cautionary tale really, not a bug with the new rails. However this does reflect my experience with certain types of rails errors really don''t point you at the source of your problem - not sure how that might be improved ... 2.the fade out is now working again - seems that one misnamed div was blocking the fade operation - not the div that was being faded, but an internal one to that - presumably the internal div error prevented the outer div from being faded. So there we go - I hope this information may be of some help to others, not just as an example of my sloppiness ... CHEERS> SAM Sam Joseph wrote:> Hi Jeremy, > > Thanks for the link to the book. > > I had a couple of issues when I upgraded: > > 1. the "/" route now fails - I get "ActionController::RoutingError > (Recognition failed for "/"):" and also this error in the log: > > Rendering > d:/ruby/lib/ruby/gems/1.8/gems/actionpack-1.10.2/lib/action_controller/templates/rescues/layout.rhtml > (404 Pag > e Not Found) > > I have tried both of the following in routes.rb to no avail: > > map.connect ''/'', :controller => ''stories'', :action => ''list'', :title > => ''Welcome'' > map.connect '''', :controller => ''stories'', :action => ''list'', :title > => ''Welcome'' > > the latter is the original one I had before the upgrade > > > 2. some scriptalicious components that worked before now fail. I use > the following to delete items: > > <%= link_to_remote "Remove", > :url=>{ > :controller=>"records", > :action=>"destroy", > :id=>record.id}, > :loading=>"status(''record#{record.id}'')", > :complete=>"new Effect.Fade(''record#{record.id}'')" > %> > > the delete still works, but there is no fade out. > > Sorry if I''m missing obvious things here - but they are the two things > that have come up ... > > Many thanks in advance. > > CHEERS> SAM > > Jeremy Kemper wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I''d appreciate it if those who''ve upgraded from 0.13.1 to the 1.0 >> release candidate would offer suggestions to improve the manual: >> >> http://manuals.rubyonrails.org/read/chapter/121 >> >> What''s unclear, not covered, broken? Gotchas, tips? >> >> Many thanks, >> jeremy >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.2 (Darwin) >> >> iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5 >> LvhioOxCDTVbZPRn0tn/dWk>> =5Awp >> -----END PGP SIGNATURE----- >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> >> > > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > >
So I managed to fix this one too.
Seems that I needed the following:
class History < ActiveRecord::Base
set_table_name "log"
set_primary_key "log_id"
end
obvious when I tried to do a show of one of these histories, rather than
a list, but again the first error really didn''t help me work out what
was actually wrong.
Hopefully if someone ever comes across the same error they can search
the mail list and find my solution ...
CHEERS> SAM
Sam Joseph wrote:
> So a follow up here - despite now having scaffolded history the
> following:
>
> class History < ActiveRecord::Base
> set_table_name "log"
> end
>
> generates the following error:
>
> undefined local variable or method `table_name'' for
#<History:0x33323c8>
>
> and yet the exact same code works for other models ...
>
> kudos if anyone can figure this out ....
>
> CHEERS> SAM
>
> Sam Joseph wrote:
>
>> Okay, so I worked around this, but it seems like 0.14.2 is kind of
>> stricter than before, i.e.
>>
>> I must have a table of correct name in my db to run scaffold, and I
>> must pass in both model and controller name at the command line - I
>> thought that if they were the same I could just specify one before
>> (maybe my imagination ...), but certainly I didn''t need a
matching
>> table name before.
>>
>> This new strictness is kind of irritating if I have to create dummy
>> tables each time I want to deal with some legacy name collision, like
>> the log table in our db and log in WebBrick.
>>
>> CHEERS> SAM
>>
>> Sam Joseph wrote:
>>
>>> Here''s another freaky issue that has arisen after the
upgrade.
>>>
>>> Running the following scaffold:
>>>
>>> ruby script\generate scaffold History History
>>>
>>> fails to produce any new code - I did have History files previously
>>> but I deleted all of them - the output I currently get is:
>>>
>>> D:\user\Code\ruby\prometheus>ruby script\generate scaffold
History
>>> History
>>> exists app/controllers/
>>> exists app/helpers/
>>> exists app/views/history
>>> exists test/functional/
>>> dependency model
>>> exists app/models/
>>> exists test/unit/
>>> exists test/fixtures/
>>> identical app/models/history.rb
>>> identical test/unit/history_test.rb
>>> identical test/fixtures/histories.yml
>>> error Before updating scaffolding from new DB schema, try
>>> creating a table for your model (History)
>>>
>>> The files definitely do not exist. I''ve also tried
destroying and
>>> re-creating, but only some of the files get recreated:
>>>
>>> D:\user\Code\ruby\prometheus>ruby script\destroy scaffold
History
>>> History
>>> rm public/stylesheets/scaffold.css
>>> missing app/views/layouts/history.rhtml
>>> missing app/helpers/history_helper.rb
>>> missing test/functional/history_controller_test.rb
>>> missing app/controllers/history_controller.rb
>>> missing app/views/history/edit.rhtml
>>> missing app/views/history/new.rhtml
>>> missing app/views/history/show.rhtml
>>> missing app/views/history/list.rhtml
>>> dependency model
>>> rm test/fixtures/histories.yml
>>> rm test/unit/history_test.rb
>>> rm app/models/history.rb
>>> notempty test/fixtures
>>> notempty test
>>> notempty test/unit
>>> notempty test
>>> notempty app/models
>>> notempty app
>>> notempty test/functional
>>> notempty test
>>> rmdir app/views/history
>>> notempty app/views
>>> notempty app
>>> notempty app/helpers
>>> notempty app
>>> notempty app/controllers
>>> notempty app
>>>
>>> D:\user\Code\ruby\prometheus>ruby script\generate scaffold
History
>>> History
>>> exists app/controllers/
>>> exists app/helpers/
>>> create app/views/history
>>> exists test/functional/
>>> dependency model
>>> exists app/models/
>>> exists test/unit/
>>> exists test/fixtures/
>>> create app/models/history.rb
>>> create test/unit/history_test.rb
>>> create test/fixtures/histories.yml
>>> error Before updating scaffolding from new DB schema, try
>>> creating a table for your model (History)
>>>
>>> Any help greatly appreciated.
>>>
>>> I see that there is no table in the DB schema but I am trying to
>>> make something to map to a log table that conflicts with WebBrick
-
>>> I have also tried with other table existing classes but to no avail
>>> - seems like the generate scaffold function is broken ...
>>>
>>> CHEERS> SAM
>>>
>>> Jeremy Kemper wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Hi all,
>>>>
>>>> I''d appreciate it if those who''ve upgraded
from 0.13.1 to the 1.0
>>>> release candidate would offer suggestions to improve the
manual:
>>>>
>>>> http://manuals.rubyonrails.org/read/chapter/121
>>>>
>>>> What''s unclear, not covered, broken? Gotchas, tips?
>>>>
>>>> Many thanks,
>>>> jeremy
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG v1.4.2 (Darwin)
>>>>
>>>>
iD8DBQFDZn6eAQHALep9HFYRAhyoAKCZxz2lz0EAVNraaD3xIkdNMDX37wCghNA5
>>>> LvhioOxCDTVbZPRn0tn/dWk>>>> =5Awp
>>>> -----END PGP SIGNATURE-----
>>>> _______________________________________________
>>>> Rails mailing list
>>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Rails mailing list
>>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>>
>>>
>>
>>
>> _______________________________________________
>> Rails mailing list
>> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
>> http://lists.rubyonrails.org/mailman/listinfo/rails
>>
>>
>
>
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>