On 4/20/07, Dan Korostelev <[EMAIL PROTECTED]> wrote:
>
> On 4/20/07, Erik Jones <[EMAIL PROTECTED]> wrote:
> >
> > Actually it's the word "database" that's that's throwing me, admin is
> > totally cool :)  Unless I'm missing the whole point, and I doubt that I am,
> > you guys are writing code to generate "scaffold" views and controllers for
> > projects' declared models and models are an abstraction on top of
> > databases.  For a given nice, consistent model interface, someone should be
> > able to swap out databases and even replace the underlying data model with
> > something else altogether (although if your models rely on introspection of
> > your db to determine their attributes, that last part goes out the window).
> > Don't get me wrong.  I have really high hopes for you guys as we, at my
> > company, are getting ready to port our fairly large php4 (sic) app to python
> > and, knowing that our software lead is really looking for some instant forms
> > for our data to alleviate having to write sql for random devhelp requests
> > and reports and the fact that I really want to push pylons (you could say
> > that after the last week I've spent looking at the docs and code I'm diggin'
> > it...), once you're done you may be getting some immediate feedback from the
> > commercial sector (again, hopefully).  You're not writing a database
> > adminstration piece, you're writing a data administration piece aimed at a
> > layer above databases.
> >
>
> Hm, well if you are about that. AdminPylon is a data/content
> administration tool, really.Need to make a proper description.
>
>
> --
> WBR, Dan Korostelev


Word.

-- 
Erik Jones
[EMAIL PROTECTED]

--~--~---------~--~----~------------~-------~--~----~
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