[Chicago] web2py 1.20 is out

[Tom Tobin]

On 2/4/08, Daniel Griffin <dgriff1 at gmail.com> wrote:
> Sorry if I incorrectly grouped django in there. I have heard it compared to
> Rails many many times, it does kinda push you down one path which is very
> easy if you are designing from scratch and pretty hard if you have to work
> with an existing dataset. What stops me in my tracks is the lack or support
> for composite primary keys.

Regarding the primary keys, you're correct — the built-in ORM supports
composite unique keys (via the "unique_together" setting), but not
composite primary keys.  Composite primary keys wouldn't make much
sense for the way the included ORM handles joins.  One could always
use another ORM (e.g., SQLAlchemy) with Django; again, the main
drawback is that the "contrib" apps are built to use the included
components (as they had to be built on *something*) ... but you don't
have to use them.  ^_^