Comments for Alan deLevie http://www.alandelevie.com The website of Alan deLevie Thu, 11 Mar 2010 04:39:09 +0000 http://wordpress.org/?v=2.5.1 Comment on (Another) simple web.py wiki by unkown http://www.alandelevie.com/2008/12/27/another-simple-webpy-wiki/#comment-564 unkown Thu, 04 Mar 2010 21:51:19 +0000 http://www.alandelevie.com/?p=213#comment-564 thanks but where is the database schema ?! i would like to try it thanks but where is the database schema ?!
i would like to try it

]]> Comment on Recursion-less storage of hierarchical data in a relational database by Twitter Trackbacks for Alan deLevie - Recursion-less storage of hierarchical data in a relational database [alandelevie.com] on Topsy.com http://www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database/#comment-551 Twitter Trackbacks for Alan deLevie - Recursion-less storage of hierarchical data in a relational database [alandelevie.com] on Topsy.com Tue, 09 Feb 2010 16:29:56 +0000 http://www.alandelevie.com/?p=11#comment-551 [...] Alan deLevie - Recursion-less storage of hierarchical data in a relational database www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database – view page – cached One of the main problems with using a relational database such as MySQL is that it can be tricky to store and retrieve hierarchical information. [...] [...] Alan deLevie - Recursion-less storage of hierarchical data in a relational database http://www.alandelevie.com/2008/07/12/recursion-less-storage-of-hierarchical-data-in-a-relational-database – view page – cached One of the main problems with using a relational database such as MySQL is that it can be tricky to store and retrieve hierarchical information. [...]

]]> Comment on From ActiveRecord to Raw SQL by admin http://www.alandelevie.com/2009/11/19/from-activerecord-to-raw-sql/#comment-546 admin Thu, 28 Jan 2010 01:10:37 +0000 http://www.alandelevie.com/?p=337#comment-546 2.3.3--but that shouldn't have anything to do with it. You're absolutely right, any finder method will return an array of objects. And you're right again about find_by_sql. I was probably thinking of ActiveRecord::Base.connection.execute('SELECT * FROM users') (source=http://www.rabbitcreative.com/2007/06/08/executing-raw-sql-in-rails/) which returns mysql objects whose attributes are returned using a hash. But thanks for the correction--I updated the post. 2.3.3–but that shouldn’t have anything to do with it.

You’re absolutely right, any finder method will return an array of objects. And you’re right again about find_by_sql. I was probably thinking of ActiveRecord::Base.connection.execute(’SELECT * FROM users’) (source=http://www.rabbitcreative.com/2007/06/08/executing-raw-sql-in-rails/) which returns mysql objects whose attributes are returned using a hash.

But thanks for the correction–I updated the post.

]]> Comment on From ActiveRecord to Raw SQL by Andrew http://www.alandelevie.com/2009/11/19/from-activerecord-to-raw-sql/#comment-545 Andrew Wed, 27 Jan 2010 07:46:25 +0000 http://www.alandelevie.com/?p=337#comment-545 Hi, What version of Rails are you using? I've never known find_by_sql to return anything other than an array of model objects. I don't even see how it's possible @posts could be a hash as they would be unordered and you also subsequently access it via an integer key (which is possible but unusual for a Hash). Regards, Andrew Hi,

What version of Rails are you using? I’ve never known find_by_sql to return anything other than an array of model objects. I don’t even see how it’s possible @posts could be a hash as they would be unordered and you also subsequently access it via an integer key (which is possible but unusual for a Hash).

Regards,
Andrew

]]> Comment on Demystifying eager loading with ActiveRecord by admin http://www.alandelevie.com/2010/01/26/demystifying-eager-loading-with-activerecord/#comment-544 admin Tue, 26 Jan 2010 18:15:05 +0000 http://www.alandelevie.com/?p=362#comment-544 I don't know what proficiency level of Ruby/Rails you guys are, but it seems that you have at least a decent amount of experience. It also seems that eager loading already makes sense to you. I started Rails last summer and one of my development partners just started Rails about a month ago. Eager loading "clicked" for me a few weeks ago, and clicked for my partner yesterday. The docs do not provide a complete picture as they only show *some* of the associations. It is up to the seasoned Rails developer to assume the rest of them. (FYI, I'm not criticizing the docs--I like them a lot.) I filled in a few small missing pieces that for at least me and one other person, made a huge difference. I don't know about you, but I spend a good deal of my debugging time trying to fix problems whose solutions are small, often, trivial changes. When first picking up Ruby/Rails, it is often the small things that bog down learning: "What are those @-signs for? or those colons? When do I use them?" A short and simple explanation is all that is needed to get the new learner back on his/her feet. But without such an explanation s/he could be stuck for hours instead of minutes. The length of the solution does not necessarily determine the significance of the problem. I don’t know what proficiency level of Ruby/Rails you guys are, but it seems that you have at least a decent amount of experience. It also seems that eager loading already makes sense to you.

I started Rails last summer and one of my development partners just started Rails about a month ago. Eager loading “clicked” for me a few weeks ago, and clicked for my partner yesterday.

The docs do not provide a complete picture as they only show *some* of the associations. It is up to the seasoned Rails developer to assume the rest of them. (FYI, I’m not criticizing the docs–I like them a lot.)

I filled in a few small missing pieces that for at least me and one other person, made a huge difference. I don’t know about you, but I spend a good deal of my debugging time trying to fix problems whose solutions are small, often, trivial changes.

When first picking up Ruby/Rails, it is often the small things that bog down learning: “What are those @-signs for? or those colons? When do I use them?” A short and simple explanation is all that is needed to get the new learner back on his/her feet. But without such an explanation s/he could be stuck for hours instead of minutes.

The length of the solution does not necessarily determine the significance of the problem.

]]> Comment on Demystifying eager loading with ActiveRecord by Some Guy http://www.alandelevie.com/2010/01/26/demystifying-eager-loading-with-activerecord/#comment-543 Some Guy Tue, 26 Jan 2010 17:34:39 +0000 http://www.alandelevie.com/?p=362#comment-543 What is the point of this blog entry? All it does is restate, verbatim, the development docs, and a provide trivial example. What is the point of this blog entry? All it does is restate, verbatim, the development docs, and a provide trivial example.

]]> Comment on Demystifying eager loading with ActiveRecord by Trent C. http://www.alandelevie.com/2010/01/26/demystifying-eager-loading-with-activerecord/#comment-542 Trent C. Tue, 26 Jan 2010 17:34:05 +0000 http://www.alandelevie.com/?p=362#comment-542 I have to agree with the first comment. This doesn't make anything more clear. There is no explanation of any kind, so the title is misleading, since if someone is mystified by something, they will probably not be demystified without an explanation of some kind. This reads more like an "Aha! When I looked at this, I suddenly understood." If someone is really mystified by eager loading, they are probably not going to suddenly understand anything from this article. I have to agree with the first comment. This doesn’t make anything more clear. There is no explanation of any kind, so the title is misleading, since if someone is mystified by something, they will probably not be demystified without an explanation of some kind.

This reads more like an “Aha! When I looked at this, I suddenly understood.” If someone is really mystified by eager loading, they are probably not going to suddenly understand anything from this article.

]]> Comment on Demystifying eager loading with ActiveRecord by admin http://www.alandelevie.com/2010/01/26/demystifying-eager-loading-with-activerecord/#comment-541 admin Tue, 26 Jan 2010 15:09:29 +0000 http://www.alandelevie.com/?p=362#comment-541 It helped me a lot as well as someone I work with. But do let me know what you don't understand, I'd be glad to try and help. -Alan It helped me a lot as well as someone I work with.

But do let me know what you don’t understand, I’d be glad to try and help.

-Alan

]]> Comment on Demystifying eager loading with ActiveRecord by Thierry B. http://www.alandelevie.com/2010/01/26/demystifying-eager-loading-with-activerecord/#comment-540 Thierry B. Tue, 26 Jan 2010 10:46:34 +0000 http://www.alandelevie.com/?p=362#comment-540 Sorry, but your explanation is too short. It doesn't make it clearer Sorry, but your explanation is too short. It doesn’t make it clearer

]]> Comment on Better project template for Google App Engine by j conroy http://www.alandelevie.com/2009/03/13/better-project-template-for-google-app-engine/#comment-536 j conroy Wed, 06 Jan 2010 01:40:17 +0000 http://www.alandelevie.com/?p=284#comment-536 Thanks-- much appreciated. you've saved a bit of time for me here regarding headers and includes (ie getting BSoup to work properly first time on GAE) ;) Thanks– much appreciated. you’ve saved a bit of time for me here regarding headers and includes (ie getting BSoup to work properly first time on GAE) ;)

]]>