Hi -- I''ve successfully run RoR on my Mac without difficulty, but getting it working on my Win2k laptop has been an unusual pain. I''ve run through the basic commands to get the one-click Ruby installer, gem and rails, and generated a scaffold. Everything looks like it does on the Mac at this point. WebBrick starts up okay. But I get errors like: ActiveRecord::StatementInvalid in Monsters#index Invalid argument: SELECT * FROM monsters app/controllers/monsters_controller.rb:8:in `list'' app/controllers/monsters_controller.rb:3:in `index'' script/server:48 I''m not sure what to make of that, basically. Any help would be greatly appreciated! Thanks! -- joshua --- Geek out: thewehners.net/joshua
On Apr 3, 2005 5:27 AM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: [RoR on windows]> WebBrick starts up okay. > > But I get errors like: > > ActiveRecord::StatementInvalid in Monsters#index > > Invalid argument: SELECT * FROM monstersThis indicates a connection problem to MySQL (unless you are using a different DB, in which case I''d suspect a connection problem to that DB but wouldn''t know for sure). Try bouncing Apache and MySQL, and see if that helps. I''ve seen this when I suspend in one network and resume in another (the Ruby bound to the FastCGI process then doens''t know how to connect to the DB). Arien
On Apr 3, 2005, at 12:27 PM, Arien Malec wrote:>> WebBrick starts up okay. >> >> But I get errors like: >> >> ActiveRecord::StatementInvalid in Monsters#index >> >> Invalid argument: SELECT * FROM monsters > > This indicates a connection problem to MySQL (unless you are using a > different DB, in which case I''d suspect a connection problem to that > DB but wouldn''t know for sure). > > Try bouncing Apache and MySQL, and see if that helps. I''ve seen this > when I suspend in one network and resume in another (the Ruby bound to > the FastCGI process then doens''t know how to connect to the DB).I appreciate the help, but I don''t think that''s all that''s going on. From a fresh start, start MySQL. Start WebBrick (not Apache, btw). Go to localhost:3000/monsters/ Response: ActiveRecord::StatementInvalid in Monsters#index Packets out of order 1<>3: SELECT * FROM monsters Kill WebBrick. Kill MySQL. Start MySQL. Start WebBrick. Go to URL. Now, I get: ActiveRecord::StatementInvalid in Monsters#index Invalid argument: SELECT * FROM monsters For what it''s worth, I *can* connect to MySQL from command line, or from PHP apps. -- joshua --- Geek out: www.thewehners.net/joshua/
Mmm. "Packets Out Of Order" rang a bell - somebody else had that problem and they solved it and posted the solution :- "I upgraded ruby (I had pre 3 1.8.2) and MySQL to 4.1.10a and am now connecting." On Apr 4, 2005 5:04 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote:> On Apr 3, 2005, at 12:27 PM, Arien Malec wrote: > > >> WebBrick starts up okay. > >> > >> But I get errors like: > >> > >> ActiveRecord::StatementInvalid in Monsters#index > >> > >> Invalid argument: SELECT * FROM monsters > > > > This indicates a connection problem to MySQL (unless you are using a > > different DB, in which case I''d suspect a connection problem to that > > DB but wouldn''t know for sure). > > > > Try bouncing Apache and MySQL, and see if that helps. I''ve seen this > > when I suspend in one network and resume in another (the Ruby bound to > > the FastCGI process then doens''t know how to connect to the DB). > > I appreciate the help, but I don''t think that''s all that''s going on. > > From a fresh start, start MySQL. Start WebBrick (not Apache, btw). > > Go to localhost:3000/monsters/ > > Response: > > ActiveRecord::StatementInvalid in Monsters#index > > Packets out of order 1<>3: SELECT * FROM monsters > > Kill WebBrick. Kill MySQL. Start MySQL. Start WebBrick. Go to URL. Now, > I get: > > ActiveRecord::StatementInvalid in Monsters#index > > Invalid argument: SELECT * FROM monsters > > For what it''s worth, I *can* connect to MySQL from command line, or > from PHP apps. > > -- joshua > > --- > Geek out: www.thewehners.net/joshua/ > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Hi all, I''ll announce the availablity of the first version of the Upload progress patch, that Sean Treadway and i developed, read more about it on: http://mir.aculo.us/th0fu/multipart-form-upload-progress-first-release/ view A helper for easy using in your views will follow, allowing for ajax-powered progress bars. My special thanks to Sean Treadway, who made something useful out of my first attempt. Thomas
btw: We would like to hear about your results with different environments (CGI, FCGI, mod_ruby) and webservers. thx, Thomas Am 04.04.2005 um 19:42 schrieb Thomas Fuchs:> Hi all, > > I''ll announce the availablity of the first version of the Upload > progress patch, that Sean Treadway and i developed, > read more about it on: > > http://mir.aculo.us/th0fu/multipart-form-upload-progress-first- > release/view > > A helper for easy using in your views will follow, allowing for > ajax-powered progress bars. > > My special thanks to Sean Treadway, who made something useful out of > my first attempt. > > Thomas > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Hmmm... Nope, that''s not doing it. E:\html\new_monsters_ruby>ruby -v ruby 1.8.2 (2004-12-25) [i386-mswin32] E:\html\new_monsters_ruby>mysql -uroot -p Enter password: ****** Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 4.1.10a Type ''help;'' or ''\h'' for help. Type ''\c'' to clear the buffer. mysql> quit; Bye Although, I haven''t seen "Packets out of order" in a while, I''m getting nothing but "Invalid argument: SELECT * FROM monsters" I''m not sure I even understand that error message: What is that SQL string a bad argument to? -- joshua --- Geek out: www.thewehners.net/joshua/ On Apr 4, 2005, at 12:08 PM, Glenn Smith wrote:> Mmm. "Packets Out Of Order" rang a bell - somebody else had that > problem and they solved it and posted the solution :- > > "I upgraded ruby (I had pre 3 1.8.2) and MySQL to 4.1.10a and am now > connecting." > > > > > On Apr 4, 2005 5:04 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: >> On Apr 3, 2005, at 12:27 PM, Arien Malec wrote: >> >>>> WebBrick starts up okay. >>>> >>>> But I get errors like: >>>> >>>> ActiveRecord::StatementInvalid in Monsters#index >>>> >>>> Invalid argument: SELECT * FROM monsters >>> >>> This indicates a connection problem to MySQL (unless you are using a >>> different DB, in which case I''d suspect a connection problem to that >>> DB but wouldn''t know for sure). >>> >>> Try bouncing Apache and MySQL, and see if that helps. I''ve seen this >>> when I suspend in one network and resume in another (the Ruby bound >>> to >>> the FastCGI process then doens''t know how to connect to the DB). >> >> I appreciate the help, but I don''t think that''s all that''s going on. >> >> From a fresh start, start MySQL. Start WebBrick (not Apache, btw). >> >> Go to localhost:3000/monsters/ >> >> Response: >> >> ActiveRecord::StatementInvalid in Monsters#index >> >> Packets out of order 1<>3: SELECT * FROM monsters >> >> Kill WebBrick. Kill MySQL. Start MySQL. Start WebBrick. Go to URL. >> Now, >> I get: >> >> ActiveRecord::StatementInvalid in Monsters#index >> >> Invalid argument: SELECT * FROM monsters >> >> For what it''s worth, I *can* connect to MySQL from command line, or >> from PHP apps. >> >> -- joshua >> >> --- >> Geek out: www.thewehners.net/joshua/ >> >> _______________________________________________ >> 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
For what it''s worth: I got this resolved. It appears to have been an issue with MySQL passwords. The password Ruby was sending wasn''t working. Setting up a non-password user is a workaround for now (this is just a development laptop). I suspect this has something to do with a change in password methods in MySQL >= 4.1(see http://dev.mysql.com/doc/mysql/en/password-hashing.html ). -- joshua --- Geek out: www.thewehners.net/joshua/ On Apr 5, 2005, at 10:08 AM, Joshua Wehner wrote:> Hmmm... Nope, that''s not doing it. > > E:\html\new_monsters_ruby>ruby -v > ruby 1.8.2 (2004-12-25) [i386-mswin32] > > E:\html\new_monsters_ruby>mysql -uroot -p > Enter password: ****** > Welcome to the MySQL monitor. Commands end with ; or \g. > Your MySQL connection id is 2 to server version: 4.1.10a > > Type ''help;'' or ''\h'' for help. Type ''\c'' to clear the buffer. > > mysql> quit; > Bye > > > Although, I haven''t seen "Packets out of order" in a while, I''m > getting nothing but "Invalid argument: SELECT * FROM monsters" > > I''m not sure I even understand that error message: What is that SQL > string a bad argument to? > > > -- joshua > > > --- > Geek out: www.thewehners.net/joshua/ > > On Apr 4, 2005, at 12:08 PM, Glenn Smith wrote: > >> Mmm. "Packets Out Of Order" rang a bell - somebody else had that >> problem and they solved it and posted the solution :- >> >> "I upgraded ruby (I had pre 3 1.8.2) and MySQL to 4.1.10a and am now >> connecting." >> >> >> >> >> On Apr 4, 2005 5:04 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: >>> On Apr 3, 2005, at 12:27 PM, Arien Malec wrote: >>> >>>>> WebBrick starts up okay. >>>>> >>>>> But I get errors like: >>>>> >>>>> ActiveRecord::StatementInvalid in Monsters#index >>>>> >>>>> Invalid argument: SELECT * FROM monsters >>>> >>>> This indicates a connection problem to MySQL (unless you are using a >>>> different DB, in which case I''d suspect a connection problem to that >>>> DB but wouldn''t know for sure). >>>> >>>> Try bouncing Apache and MySQL, and see if that helps. I''ve seen this >>>> when I suspend in one network and resume in another (the Ruby bound >>>> to >>>> the FastCGI process then doens''t know how to connect to the DB). >>> >>> I appreciate the help, but I don''t think that''s all that''s going on. >>> >>> From a fresh start, start MySQL. Start WebBrick (not Apache, btw). >>> >>> Go to localhost:3000/monsters/ >>> >>> Response: >>> >>> ActiveRecord::StatementInvalid in Monsters#index >>> >>> Packets out of order 1<>3: SELECT * FROM monsters >>> >>> Kill WebBrick. Kill MySQL. Start MySQL. Start WebBrick. Go to URL. >>> Now, >>> I get: >>> >>> ActiveRecord::StatementInvalid in Monsters#index >>> >>> Invalid argument: SELECT * FROM monsters >>> >>> For what it''s worth, I *can* connect to MySQL from command line, or >>> from PHP apps. >>> >>> -- joshua >>> >>> --- >>> Geek out: www.thewehners.net/joshua/ >>> >>> _______________________________________________ >>> 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
Are you using "old style" password? I has a problem w/ "old style" (not sure about the right term) password, and just set back to the "new style". regards, juca On Apr 5, 2005 6:02 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote:> > For what it''s worth: I got this resolved. It appears to have been an > issue with MySQL passwords. The password Ruby was sending wasn''t > working. Setting up a non-password user is a workaround for now (this > is just a development laptop). I suspect this has something to do with > a change in password methods in MySQL >= 4.1(see > http://dev.mysql.com/doc/mysql/en/password-hashing.html ). > > > -- joshua > > --- > Geek out: www.thewehners.net/joshua/ <http://www.thewehners.net/joshua/> > > On Apr 5, 2005, at 10:08 AM, Joshua Wehner wrote: > > > Hmmm... Nope, that''s not doing it. > > > > E:\html\new_monsters_ruby>ruby -v > > ruby 1.8.2 (2004-12-25) [i386-mswin32] > > > > E:\html\new_monsters_ruby>mysql -uroot -p > > Enter password: ****** > > Welcome to the MySQL monitor. Commands end with ; or \g. > > Your MySQL connection id is 2 to server version: 4.1.10a > > > > Type ''help;'' or ''\h'' for help. Type ''\c'' to clear the buffer. > > > > mysql> quit; > > Bye > > > > > > Although, I haven''t seen "Packets out of order" in a while, I''m > > getting nothing but "Invalid argument: SELECT * FROM monsters" > > > > I''m not sure I even understand that error message: What is that SQL > > string a bad argument to? > > > > > > -- joshua > > > > > > --- > > Geek out: www.thewehners.net/joshua/ <http://www.thewehners.net/joshua/> > > > > On Apr 4, 2005, at 12:08 PM, Glenn Smith wrote: > > > >> Mmm. "Packets Out Of Order" rang a bell - somebody else had that > >> problem and they solved it and posted the solution :- > >> > >> "I upgraded ruby (I had pre 3 1.8.2) and MySQL to 4.1.10a and am now > >> connecting." > >> > >> > >> > >> > >> On Apr 4, 2005 5:04 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: > >>> On Apr 3, 2005, at 12:27 PM, Arien Malec wrote: > >>> > >>>>> WebBrick starts up okay. > >>>>> > >>>>> But I get errors like: > >>>>> > >>>>> ActiveRecord::StatementInvalid in Monsters#index > >>>>> > >>>>> Invalid argument: SELECT * FROM monsters > >>>> > >>>> This indicates a connection problem to MySQL (unless you are using a > >>>> different DB, in which case I''d suspect a connection problem to that > >>>> DB but wouldn''t know for sure). > >>>> > >>>> Try bouncing Apache and MySQL, and see if that helps. I''ve seen this > >>>> when I suspend in one network and resume in another (the Ruby bound > >>>> to > >>>> the FastCGI process then doens''t know how to connect to the DB). > >>> > >>> I appreciate the help, but I don''t think that''s all that''s going on. > >>> > >>> From a fresh start, start MySQL. Start WebBrick (not Apache, btw). > >>> > >>> Go to localhost:3000/monsters/ > >>> > >>> Response: > >>> > >>> ActiveRecord::StatementInvalid in Monsters#index > >>> > >>> Packets out of order 1<>3: SELECT * FROM monsters > >>> > >>> Kill WebBrick. Kill MySQL. Start MySQL. Start WebBrick. Go to URL. > >>> Now, > >>> I get: > >>> > >>> ActiveRecord::StatementInvalid in Monsters#index > >>> > >>> Invalid argument: SELECT * FROM monsters > >>> > >>> For what it''s worth, I *can* connect to MySQL from command line, or > >>> from PHP apps. > >>> > >>> -- joshua > >>> > >>> --- > >>> Geek out: www.thewehners.net/joshua/<http://www.thewehners.net/joshua/> > >>> > >>> _______________________________________________ > >>> 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 >-- juraci krohling costa http://jkcosta.info _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On Apr 6, 2005, at 7:23 AM, Juraci Krohling Costa wrote:> Are you using "old style" password? I has a problem w/ "old style" > (not sure about the right term) password, and just set back to the > "new style". > > regards, > juca > > On Apr 5, 2005 6:02 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: >> For what it''s worth: I got this resolved. It appears to have been an >> issue with MySQL passwords. The password Ruby was sending wasn''t >> working. Setting up a non-password user is a workaround for now (this >> is just a development laptop). I suspect this has something to do with >> a change in password methods in MySQL >= 4.1(see >> http://dev.mysql.com/doc/mysql/en/password-hashing.html ). >>Yes, that is, basically, what I''m talking about. The conflict/problem is that I''m still doing PHP development on this box (which requires old style passwords) and Rails appears to require new style passwords. I solved it by used a no-password ruby user in MySQL, but that wouldn''t work in a development environment. -- joshua --- Geek out: www.thewehners.net/joshua/
Ah, ok :-) I solved this by quitting php development =D On Apr 6, 2005 10:34 AM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote:> > On Apr 6, 2005, at 7:23 AM, Juraci Krohling Costa wrote: > > > Are you using "old style" password? I has a problem w/ "old style" > > (not sure about the right term) password, and just set back to the > > "new style". > > > > regards, > > juca > > > > On Apr 5, 2005 6:02 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: > >> For what it''s worth: I got this resolved. It appears to have been an > >> issue with MySQL passwords. The password Ruby was sending wasn''t > >> working. Setting up a non-password user is a workaround for now (this > >> is just a development laptop). I suspect this has something to do with > >> a change in password methods in MySQL >= 4.1(see > >> http://dev.mysql.com/doc/mysql/en/password-hashing.html ). > >> > > Yes, that is, basically, what I''m talking about. The conflict/problem > is that I''m still doing PHP development on this box (which requires old > style passwords) and Rails appears to require new style passwords. I > solved it by used a no-password ruby user in MySQL, but that wouldn''t > work in a development environment. > > > -- joshua > > --- > Geek out: www.thewehners.net/joshua/ <http://www.thewehners.net/joshua/> > >-- juraci krohling costa http://jkcosta.info _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
> -----Original Message----- > From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails- > bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Joshua Wehner > Sent: Wednesday, April 06, 2005 9:34 AM > To: Juraci Krohling Costa; rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > Subject: Re: [Rails] Rails on Windows? > > On Apr 6, 2005, at 7:23 AM, Juraci Krohling Costa wrote: > > > Are you using "old style" password? I has a problem w/ "old style" > > (not sure about the right term) password, and just set back to the > > "new style". > > > > regards, > > juca > > > > On Apr 5, 2005 6:02 PM, Joshua Wehner <joshua-AnsgPkSrJBbs2Lz0fTdYFQ@public.gmane.org> wrote: > >> For what it''s worth: I got this resolved. It appears to have been an > >> issue with MySQL passwords. The password Ruby was sending wasn''t > >> working. Setting up a non-password user is a workaround for now (this > >> is just a development laptop). I suspect this has something to do with > >> a change in password methods in MySQL >= 4.1(see > >> http://dev.mysql.com/doc/mysql/en/password-hashing.html ). > >> > > > Yes, that is, basically, what I''m talking about. The conflict/problem > is that I''m still doing PHP development on this box (which requires old > style passwords) and Rails appears to require new style passwords. I > solved it by used a no-password ruby user in MySQL, but that wouldn''t > work in a development environment.I solved a similar problem here by telling MySQL to use the "old style" passwords for the system. If it''s just one application, you can use a SQL function ( "OLD_PASSWORD()" ) to generate a short hash that is compatible with older code for that user. Soulhuntre ---------- http://www.girl2.com - my girls http://www.the-estate.com - my legacy http://wiki.thegreybook.com - my project http://weblog.soulhuntre.com - my thoughts> > > > -- joshua > > --- > Geek out: www.thewehners.net/joshua/ > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
On 4 Apr 2005, at 17:04, Joshua Wehner wrote:> ActiveRecord::StatementInvalid in Monsters#index > > Packets out of order 1<>3: SELECT * FROM monstersI know you''ve been given the OLD_PASSWORD solution, but there''s another one I got from someone on the IRC channel and posted on the wiki a few days ago: http://wiki.rubyonrails.com/rails/show/ MySQL%20Database%20access%20problem Look at the bottom of the page. Cheers, Pete