Comments for Tech Raving

Comment on Download Counter WP Plugin by hendra

hendra — Thu, 11 Jun 2009 04:16:27 +0000

good share. thank’s man

Comment on CherryPy, RESTFul Routing by Titusz

Titusz — Mon, 20 Apr 2009 15:50:57 +0000

thanks for this nice example… very usefull. i found that when i use cherrypy.dispatch.MethodDispatcher(), and send a request with a not implemented method for a controlor, it will answer with a nice 405 Method Not Allowed - including the allowed methods for the requested URI … how would you do this with your approach, when using custom routes?

Comment on Google Is Actually Responsible by Mouseclone

Mouseclone — Tue, 17 Mar 2009 00:03:20 +0000

I had no idea it had affected you that much. I’m glad I could help, and would you believe I stopped by the site because of the linkback? Just going to some old data, though I would stop by and say hello.

Comment on CakePHP RESTFul Resources, Not There Yet. by Matt Curry

Matt Curry — Thu, 05 Mar 2009 18:29:09 +0000

Yea, I understand all that. It just sounded weird, because I’ve never heard of a REST request returning an HTML form.

Comment on CakePHP RESTFul Resources, Not There Yet. by ScottK

ScottK — Thu, 05 Mar 2009 17:43:56 +0000

By default the new/edit action in the PostsController renders the new.ctp/edit.ctp respectively.

The new.ctp would hold all the model fields you wish to collect when creating a new record. The edit.ctp would display all the fields for an exiting record for modification.

Typically you would only produce html files for these.

Comment on CakePHP RESTFul Resources, Not There Yet. by Matt Curry

Matt Curry — Thu, 05 Mar 2009 17:28:05 +0000

Hey Scott,
I’m a bit confused over what’s returned when you make a GET request to /posts/new or /posts/1/edit. Is it the actual HTML with the inputs or some XML representation?

Comment on I’ve updated the PyMigrate test by ScottK

ScottK — Sat, 14 Feb 2009 21:18:58 +0000

I’ve begun to look at integrating SA and see that SA needs to be aware of the table structure. From my tests I think that SqlAlchemy is the way to go as it supports so many different database types.

My test units have shown that SA needs to know the existing database constructs. I just need to implement the correct conversions. One of the first thing that’s bothering me initially is that calling Column(name, String) in MySql errors the database where as Column(name, Sting(50)) works fine.

It may be something I have to deal with on my end if not in SA.

Comment on I’ve updated the PyMigrate test by mike bayer

mike bayer — Sat, 14 Feb 2009 20:32:12 +0000

why not say, metadata(create_engine(”your://database”)).reflect_all() ? no model building.

Comment on I’ve updated the PyMigrate test by ScottK

ScottK — Sat, 14 Feb 2009 12:48:02 +0000

I hadn’t learned of sqlalchemy-migrate till just a few days prior to releasing PyMigrate. So I basically had a working system.

After looking at sqlalchemy-pymigrate I didn’t like how I would have to learn sqlalchemy to format the tables as a user. Even then it seemed like a lot of work to create a table by fist building the model so SA could map it.

Truth be told though, as long as the migration format set-up is easy for the user, I’m ok with either system. I’ll look at it again and see if maybe I can help out with it.

Comment on I’ve updated the PyMigrate test by mike bayer

mike bayer — Sat, 14 Feb 2009 08:13:29 +0000

why not just contribute to the Migrate project ? They could definitely use the help. We’ve added new compilable DDL constructs in SQLA 0.6 that they’re going to want to adapt to (and you will too if you stay on SQLA as your base), so there’s work to be done all around.

Inventing a whole new PyMigrate, which is going to use SQLAlchemy just like migrate anyway, seems like a huge duplication of effort ?