Sqlalchemy, SQL Views, Sysadmin
gh
django
apps (I can count 5 now but there will be more). I am working with pg
but expect to support sqlite and mysql.
I am using SQL VIEWs and SQLAlchemy. I have a command-line i/f which
includes:
create/drop/status/sizes
and to which I will add 'load <table>' soon. I noticed there is a
ticket for
supporting VIEWs but I did not want to expose my email address to the
world.
Both SA and Django introspection work fine with the VIEWs so far but
they see them as tables in Pg ... I suppose there is some way to poke
at the
meta data to figure this out but for now, I just maintail a list of
what is what.
I contacted R Munn about the SQLAlchemy integration in January but I
understand he has dropped it. I would like to volunteer as a guinea
pig for testing once someone takes this on ... but figuring this out
via google is a
pain.
It would be nice if there were an 'announce' list to let people know
things like who is working on what but I will stay subscribed to dev
for the
time being.
It seems the most straight-forward way to be in the loop at the moment
is to create a blog (and perhaps subscribe to the RSS feed from your
blog
page) so I may do that as time allows.
--gh
James Bennett
> I contacted R Munn about the SQLAlchemy integration in January but I
> understand he has dropped it. I would like to volunteer as a guinea
> pig for testing once someone takes this on ... but figuring this out
> via google is a
> pain.
If half as many people would volunteer to write code as volunteer to
"test SQLAlchemy integration when someone else writes it", we would
have had the feature approximately 300 years ago ;)
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Guy Hulbert
> On 6/4/07, gh <gwhu...@eol.ca> wrote:
> > I contacted R Munn about the SQLAlchemy integration in January but I
> > understand he has dropped it. I would like to volunteer as a guinea
> > pig for testing once someone takes this on ... but figuring this out
> > via google is a
> > pain.
>
> If half as many people would volunteer to write code as volunteer to
> "test SQLAlchemy integration when someone else writes it", we would
> have had the feature approximately 300 years ago ;)
[ sorry about the goo-formatting on the original mail ]
I said 3 months ... I will have started by the end of that period ...
probably something you want to avoid ;-).
I will take this as "no-one is working on it".
In the Aug 29, 2006 thread:
http://groups.google.com/group/django-developers/browse_thread/thread/5149e1c60dc65bff/a177bb34cfde1ec7
I find two different implementations planned[*]:
One:
In other words,
SQLAlchemy models would be instances of
django.contrib.sqlalchemy.db.models.Model rather than
django.db.models.Model.
Two:
* This branch will be called "sqlalchemy" in the Django
Subversion repository.
[*] I suppose this was unintentional ;-)
There is no: django.contrib.sqlalchemy.db.models.Model here:
http://code.djangoproject.com/browser/django/trunk/django/contrib
but there is a 'sqlalchemy' branch.
I can work on django.contrib.sqlalchemy.db.models.Model without SVN
access so that is what I plan to do.
If someone would like things to go faster and takes on the 'sqlalchemy'
branch then let me know (starting django-announce would help :-) and I
will work with them ... or do what I am told.
>
--
--gh
Guy Hulbert
> I can work on django.contrib.sqlalchemy.db.models.Model without SVN
> access so that is what I plan to do.
>
> If someone would like things to go faster and takes on the
> 'sqlalchemy'
> branch then let me know (starting django-announce would help :-) and I
> will work with them ... or do what I am told.
It seems that my email address can be retrieved via the 'view profile'
link in the google groups interface so I am going to stop reading now.
I'll join the list again if I make any progress.
I'd appreciate being contacted by anyone who plans to take up the
sqlalchemy branch.
--
--gh