On 4/19/07, Sean Davis <[EMAIL PROTECTED]> wrote:
>
>
> On 4/19/07, durumdara <[EMAIL PROTECTED]> wrote:
> >
> > > ActiveRecord is a Ruby-on-Rails concept, although there are parallel
> ideas
> > > in any Object-Relational-Mapper, of which SQLObject and SQLAlchemy are
> two.
> > >
> > >####There are not predefined views####
> > >
> > >based on these in Pylons.  You can certainly
> > > write an application that uses an ORM for database access, but this
> isn't
> > > required.
> >
> > So there is no any view/template to show records, or edit them simply?
> > I need to define them all?
> >
> > In modpy that was the problem too, I need to make my formbuilder tools
> > to simplify the editing/showing of records, handle lookups (foreign
> > keys), etc.
> >
> > What the module/library/package used by the pylon-masters to solve
> > this problem?
> > (To avoid recreation of reports in every search for, and to centralize/
> > globalize the handling of reports/data forms).
>
> There is a discussion on this list called "automatic database administration
> tool" that you might want to read.  Pylons does not include these tools
> out-of-the-box.

In TurboGears, they have CatWalk, but it's for SQLObject.  Django has
this feature as well.  Pylons doesn't.  When I chose Pylons, I felt
that it had benefits that were more important than this one feature.
But, your mileage may vary.  If this is a feature that you absolutely
must have, I suggest Django.  I don't use Django because I really
dislike the templating engine, and I prefer to use SQLAlchemy.
Nothing is perfect ;)

Best Regards,
-jj

-- 
http://jjinux.blogspot.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to