> Fortunately, a pre-runtime hook gives anybody who wants it the ability
> to add this signal for their own use anyway, so the initial problem
> solution solves everything.
>
Good point. You win this round...
--~--~-~--~~~---~--~~
You received this message because
Two things.
The preruntime hook is a pretty good idea. Something to think about
though is providing a way to add callbacks to this hook that is
independant of settings.py. Otherwise 3rd party apps that want the
functionality would require changes to the settings.py beyond the
INSTALLED_APPS tuple
Due to popular demand, you can use your Django models as the ORM objects.
I'm in the process of filling out some documentation on the wiki. If
anyone has any comments or suggestions I'd like to hear them.
All in all, adding SQLAlchemy to your Django project takes three lines of code.
Pa
f you're worried about the overhead of creating
objects for each row, then maybe you should look into using the raw
DB-API to get your data.
Paul Davis
On 10/6/07, Norjee <[EMAIL PROTECTED]> wrote:
>
> Hi from the Jeroen guy ;)
>
> As you can see my version of mixing sqla
re I could envisage using SA and django ORM side by
> side.
> That way you won't have to mess with any of your views/admin/django core
> functionality, as the underlying objects are still just django models.
>
> What do you think?
>
> Ben
>
> On 06/10/2007, Paul Da
o import
one or the other depending on what you plan on doing. For instance all
of my code will use just the SA models, but the admin will still use
the Django models.
Paul
On 10/5/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
>
>
> On Oct 6, 5:24 am, "Paul Davis" &l
the description at the URL you posted it
seems quite a bit more clunky to use, but he does do some of the
things I had initially planned on doing.
Thanks for the heads on the project. I hadn't heard of it.
Paul Davis
On 10/4/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> Hi Paul,
>
&
suming tranquil is in the installed apps, just do:
from tranquil.models.app_name import ModelName
ModelName is the SQLAlchemy ORM object which means its pure SQLAlchemy
from there.
Any feedback is welcome. If there's enough interest I'll move forward
with filling o
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> Paul Davis wrote:
> >
> > As near as I can tell these are the main issues that don't seem to be
> resolved:
> >
> > 1. Balancing ease of use with power of use (Ie, Alice vs. Carol)
> >
ersion
individual lines in a file. I mean, not even CVS is that bad.
=
In order to keep things short this is all I'm gonna say for now. This
email is already too long.
Thanks,
Paul Davis
--~--~-~--~~~---~--~~
You received this message because
On 9/5/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 9/6/07, Paul Davis <[EMAIL PROTECTED]> wrote:
> >
> > I'm having a bit of a problem using the appname/sql/model.sql custom
> > sql files.
> ...
> > But running:
> > $ python
eing run in a single transaction like I would think it should
if I can't specificaly order my scripts so that I populate tables that
are referenced by foreign keys first.
Plus, I'd assume this is a big reason why all the constraints are
deferred too.
So, anyone have any insights?
Than
d one the way django.contrib.admin is doing.
> http://dpaste.com/17864/
>
> Deepak
>
>
And I vote yes to including a version similar to yours.
Paul Davis
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&qu
project, this was one of the major stumbling blocks for me.
(Which I think is about as good of an endorsement for django as any
other)
[1] http://www.djangosnippets.org/snippets/394/
Paul Davis
--~--~-~--~~~---~--~~
You received this message because you are sub
14 matches
Mail list logo
