Re: About *Fields, newforms and lazyness
2007/3/6, David Larlet <[EMAIL PROTECTED]>:
> Hi,
>
> I got some troubles today with newforms. I use to create models fields
> with a first implicit verbose_name argument:
> email = models.EmailField("E-mail")
>
> Unfortunately newforms fields have quite similar argument (label) but
> it's not the first argument. Moreover, it's a bit annoying because I
> got an UnicodeError which drive me crazy before I verify the argument
> order.
>
> I know it's easy to type label= for all newforms fields but maybe we
> can reorder arguments in newforms before 0.96? What's your opinion
> about that? Am I the only one?
>
> Cheers,
> David
>
No more thoughts about this proposal? My co-worker has just done the
same mistake yesterday :-).
Cheers,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
Re: mysql_old backend
Please, check this: http://code.djangoproject.com/ticket/3775 On 21 maalis, 06:25, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > For the possibly 3.2 people who don't also subscribe to django-users, I > just posted this > > http://groups.google.com/group/django-users/browse_frm/thread/98e6857... > > describing a way to work around the forced upgrade of MySQLdb if you > cannot do it immediately. > > Regards, > Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: mysql_old backend
On Wed, Mar 21, Karsu wrote: > > Please, check this: http://code.djangoproject.com/ticket/3775 I don't think the patch--as it is--is a good idea, but what's your problem? Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
SQL Alchemy integration
Hello everybody, Is there any update about the SQL Alchemy integration ? I have checked out the sqlalchemy branch but there is not reference to SQL Alchemy in it. Cheers, Emeka --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Memory Leak with httpd.exe on Windows
Hi, I'm running a developmental Django machine with the following specs: - Windows XP - Apache - Mod_python - Django 0.95 And it appears that one of the Apache-related Windows service httpd.exe keeps on growing in memory. Has anyone encountered this problem or even know how to remedy it? Thanks, Moses --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: SQL Alchemy integration
On Wed, Mar 21, Emeka Mosanya wrote: > Hello everybody, > > Is there any update about the SQL Alchemy integration ? > I have checked out the sqlalchemy branch but there is not reference to SQL > Alchemy in it. I think this branch has only seen merges from trunk. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Memory Leak with httpd.exe on Windows
On 3/21/07, Moses Ting <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm running a developmental Django machine with the following specs: > > - Windows XP > - Apache > - Mod_python > - Django 0.95 > > And it appears that one of the Apache-related Windows service > httpd.exe keeps on growing in memory. Has anyone encountered this > problem or even know how to remedy it? > Maybe it's related to this http://www.djangoproject.com/documentation/faq/#why-is-django-leaking-memory ? Regards, -- Ramiro Morales --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: mysql_old backend
I underestand that mysql_old is compatible support for people who can't upgrade MySQLdb immediately. Without this patch I can't use django with mysql with older version than MySQLdb-1.2.1p2. If I try to use mysql_old and run python manage.py syncdb it will raise ImportError? "MySQLdb-1.2.1p2 or newer is required;". Problem is mysql_old 'introspection.py' imports from django.db.backends.mysql.base import quote_name not from django.db.backends.mysql_old.base import quote_name file. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: SQL Alchemy integration
On 3/21/07, Emeka Mosanya <[EMAIL PROTECTED]> wrote: > Is there any update about the SQL Alchemy integration ? > I have checked out the sqlalchemy branch but there is not reference to SQL > Alchemy in it. It's sleeping right now. The upcoming refactoring of Django's QuerySet mechanism looks like it'll make working with other ORMs a bit easier, so if someone wants to come back and revisit it then it'd be a bit less of an ambitious project ;) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
feature request: user session
Hi, Django has anonymous sessions, tracked by cookies. The session can not be accessed from a different machine for the same user, which drastically reduces the usefulness of sessions. Another approach to save something persistently for a user it to update the UserProfile model and create a new row for the same, but this will require altering the corresponding table every time we realize we have one more thing to save. I have proposed a solution for this, which I am going to code in couple of days, but in the meanwhile I would like to hear your feedback. http://code.djangoproject.com/ticket/3776 [little more info, about how I intend to implement is in the ticket]. -- Amit Upadhyay Blog: http://www.rootshell.be/~upadhyay +91-9820-295-512 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: feature request: user session
On Wed, Mar 21, Amit Upadhyay wrote: > Hi, > > Django has anonymous sessions, tracked by cookies. The session can not be > accessed from a different machine for the same user What do you mean with 'accessed from a different machine'? Another server (in a load balancer or similar), or another client? Both isn't true. > which drastically > reduces the usefulness of sessions. Another approach to save something > persistently for a user it to update the UserProfile model and create a new > row for the same, but this will require altering the corresponding table > every time we realize we have one more thing to save. I probably simply don't get what you try to do. Can you give an example, please? Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: feature request: user session
On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 21, Amit Upadhyay wrote: > > > Hi, > > > > Django has anonymous sessions, tracked by cookies. The session can not > be > > accessed from a different machine for the same user > > What do you mean with 'accessed from a different machine'? Another server > (in a load balancer or similar), or another client? Both isn't true. I mean from a different client/browser. > which drastically > > reduces the usefulness of sessions. Another approach to save something > > persistently for a user it to update the UserProfile model and create a > new > > row for the same, but this will require altering the corresponding table > > every time we realize we have one more thing to save. > > I probably simply don't get what you try to do. Can you give an example, > please? I have for example, lots of notifications to users, like show popup for this and show popup for that. The thing is user may not be interested in a lot of these popups [consider firefox's message: you are about to submit a data on unencrypted connection, are you want to proceed?"] and we want to put a checkbox in those dialog's saying "do not show this message again". I want to store this information somewhere, and currently I am doing it in UserProfile model of mine, but as things keep on getting added it becomes more unwieldy. Putting everything in a separate model removes the context of each settings, and makes documentation difficult, while if things are in sessions, only a set of views responsible for the given page on which we are showing the popup, and ajax handlers for it, will have to know about settings related to that page. No need to alter tables. Session is the right place for a lot of these things, (for if not, what is session suitable for?) but the current django session is not persistent, which leads to my this request. -- Amit Upadhyay Blog: http://www.rootshell.be/~upadhyay +91-9820-295-512 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: feature request: user session
But if you want reliable persistance you are going to have to store it in the DB at some stage anyway. And why not store it AND put it in the session each time you create a new session? On Wed, 21 Mar 2007 16:51:27 -, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote: >> >> On Wed, Mar 21, Amit Upadhyay wrote: >> >> > Hi, >> > >> > Django has anonymous sessions, tracked by cookies. The session can not >> be >> > accessed from a different machine for the same user >> >> What do you mean with 'accessed from a different machine'? Another >> server >> (in a load balancer or similar), or another client? Both isn't true. > > > I mean from a different client/browser. > > >> which drastically >> > reduces the usefulness of sessions. Another approach to save something >> > persistently for a user it to update the UserProfile model and create >> a >> new >> > row for the same, but this will require altering the corresponding >> table >> > every time we realize we have one more thing to save. >> >> I probably simply don't get what you try to do. Can you give an example, >> please? > > > I have for example, lots of notifications to users, like show popup for > this > and show popup for that. The thing is user may not be interested in a > lot of > these popups [consider firefox's message: you are about to submit a data > on > unencrypted connection, are you want to proceed?"] and we want to put a > checkbox in those dialog's saying "do not show this message again". I > want > to store this information somewhere, and currently I am doing it in > UserProfile model of mine, but as things keep on getting added it becomes > more unwieldy. Putting everything in a separate model removes the > context of > each settings, and makes documentation difficult, while if things are in > sessions, only a set of views responsible for the given page on which we > are > showing the popup, and ajax handlers for it, will have to know about > settings related to that page. No need to alter tables. > > Session is the right place for a lot of these things, (for if not, what > is > session suitable for?) but the current django session is not persistent, > which leads to my this request. > -- http://belfast.no-ip.info/ Get http://www.ubuntu.com/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: SQL Alchemy integration
> It's sleeping right now. The upcoming refactoring of Django's QuerySet > mechanism looks like it'll make working with other ORMs a bit easier, > so if someone wants to come back and revisit it then it'd be a bit > less of an ambitious project ;) Is there any place (e.g. a trac page) where interested parties can check out the progress on the QuerySet refactor? Since I recently completed PostGIS integration for the GeoDjango branch (will be committed to SVN branch pending Jeremy Dunck's approval), I have an active interest in what you guys plan on doing in there. On a related note, Brian Beck has some implementation ideas on how he'd go about integrating SQLAlchemy: http://blog.case.edu/bmb12/2007/03/thinking_about_taking_over_the_djangosqlalchemy_branch --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: feature request: user session
On Wed, Mar 21, Amit Upadhyay wrote: > On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > > > On Wed, Mar 21, Amit Upadhyay wrote: > > > > > Hi, > > > > > > Django has anonymous sessions, tracked by cookies. The session can not > > be > > > accessed from a different machine for the same user > > > > What do you mean with 'accessed from a different machine'? Another server > > (in a load balancer or similar), or another client? Both isn't true. > > > I mean from a different client/browser. OK, that's really not possible (at least not easily). But Django's sessions are a general-purpose session tracker. They are anonymous and don't need to be linked to a user. So, when a user uses two browsers, he gets two different sessions. Since the relation to the user is held within the pickled data in session_data, you're not able to find the other session. But you could in a different table track which session belongs to which user, and then re-use the session. I'm not sure whether this is a good idea ... Django sessions are not really designed for your purpose. > I have for example, lots of notifications to users, like show popup for this > and show popup for that. The thing is user may not be interested in a lot of > these popups [consider firefox's message: you are about to submit a data on > unencrypted connection, are you want to proceed?"] and we want to put a > checkbox in those dialog's saying "do not show this message again". I want > to store this information somewhere, and currently I am doing it in > UserProfile model of mine, but as things keep on getting added it becomes > more unwieldy. Putting everything in a separate model removes the context of > each settings, and makes documentation difficult, while if things are in > sessions, only a set of views responsible for the given page on which we are > showing the popup, and ajax handlers for it, will have to know about > settings related to that page. No need to alter tables. > > Session is the right place for a lot of these things, (for if not, what is > session suitable for?) but the current django session is not persistent, > which leads to my this request. Sessions are for light-weight stuff that does not need to be stored permanently. A user profile might suite your task much better. Each setting would be one attribute in the user profile. I don't see how the session were a better place than the user profile, but, hey, it's your web site ;-) If you find altering the database tables is a problem, you could use a user profile with just the user id and the pickled settings. Perhaps you'd like to write a middleware that fetches the settings from the profile, unpickles them and adds a settings object to the request. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: SQL Alchemy integration
On 3/21/07, jbronn <[EMAIL PROTECTED]> wrote: > Is there any place (e.g. a trac page) where interested parties can > check out the progress on the QuerySet refactor? Since I recently > completed PostGIS integration for the GeoDjango branch (will be > committed to SVN branch pending Jeremy Dunck's approval), I have an > active interest in what you guys plan on doing in there. Probably the best thing is to wait for Malcolm to see this thread, and let him explain; he knows far more about it than I do :) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: feature request: user session
On 3/21/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > ... > If you find altering the database tables is a problem, you could use a user class User(... class Message(... class UserMessagePref(...): user = FK(User) message = FK(Message) muted = Boolean() No? Or is it that you don't want to show muted messages to users, even though they are anonymous (since using a different computer)? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Problem with syncdb's handling of ManyToManyFields
Howdy, folks, I'm in the process of migrating a Django project from MySQL to PostgreSQL and think I may have stumbled across a nasty bug. It relates to ManytoMany fields and the way in which syncdb creates the database tables to handle this. For full details, please see the ticket at: http://code.djangoproject.com/ticket/3779 Can anyone else confirm this so I can be sure it's not some wonky configuration on my end? - Ben --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: mysql_old backend
On Wed, 2007-03-21 at 08:03 -0700, Karsu wrote: > I underestand that mysql_old is compatible support for people who > can't upgrade MySQLdb immediately. Without this patch I can't use > django with mysql with older version than MySQLdb-1.2.1p2. > > If I try to use mysql_old and run python manage.py syncdb it will > raise ImportError? "MySQLdb-1.2.1p2 or newer is required;". > > Problem is mysql_old 'introspection.py' imports from > django.db.backends.mysql.base import quote_name not from > django.db.backends.mysql_old.base import quote_name file. I noticed that when I was testing on an older machine this morning (I don't always have access to the other machine, so I couldn't test it yesterday). I've committed a fix now. Sorry about that. Regards, Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Memory Leak with httpd.exe on Windows
Moses Ting wrote: > Hi, > > I'm running a developmental Django machine with the following specs: > > - Windows XP > - Apache > - Mod_python > - Django 0.95 > > And it appears that one of the Apache-related Windows service > httpd.exe keeps on growing in memory. Has anyone encountered this > problem or even know how to remedy it? Which version of mod_python are you using? Older versions of mod_python are known to exhibit memory leaks if used in certain ways. Ensure you are using mod_python 3.3.1. This should eliminate at least one potential source for problems. Graham --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
ORACLE - column at array pos 0 fetched with error: 1406
I am under 4697 of
http://code.djangoproject.com/svn/django/branches/boulder-oracle-sprint/
Before reporting this message as a ticked, I would like to be sure if
it is my mistake or a bug exists.
Into an x model, I defined next field:
caracter = models.CharField('Campo Character',
maxlength=10)
When I attemp to enter next data to this field in the Admin I have
next situations:
áéíóú = No problem
áéíóúa = System generates mentioned error (ORA 1406) but
complete data is saved.
áéíóaa = No problem
á¿567890 = No problem
1234567890 = No problem.
á¿5678901 = System generates mentioned error (ORA 1406) but
complete data is saved. See related error for this data below.
What I identified is that when using characters such as á, é, ¿, etc.
system seems to use two (2) characters or positions. Although data was
saved, I can not access to any record when browsing with Django. When
inserting/changing using sqlplus command, I have no problems during
commit and during query.
My Oracle variable NLS_LANG=.UTF8 and use Windows XP2.
Part of the data where error occurs is:
# or checking the Model here, neither of which is
good.
elif isinstance(field, datetime.datetime) and \
field.hour == field.minute == field.second ==
field.microsecond == 0:
yield field.date()
else:
yield field
for unresolved_row in cursor:
row = list(resolve_cols(unresolved_row))
if fill_cache:
obj, index_end = get_cached_row(self.model, row,
0)
else:
obj = self.model(*row[:index_end])
for i, k in enumerate(extra_select):
▼ Local vars
Variable Value
cursor >
extra_select []
fill_cache False
full_query 'SELECT "TESTDB_DBTEST"."ID", "TESTDB_DBTEST"."FECHA",
"TESTDB_DBTEST"."CARACTER", "TESTDB_DBTEST"."TEXTO",
"TESTDB_DBTEST"."MONTO"\n FROM "TESTDB_DBTEST" ORDER BY
"TESTDB_DBTEST"."FECHA" ASC'
get_cached_row
index_end 5
params []
resolve_cols
select ['"TESTDB_DBTEST"."ID"', '"TESTDB_DBTEST"."FECHA"',
'"TESTDB_DBTEST"."CARACTER"', '"TESTDB_DBTEST"."TEXTO"',
'"TESTDB_DBTEST"."MONTO"']
self Error in formatting:column at array pos 0 fetched with error:
1406
sql ' FROM "TESTDB_DBTEST" ORDER BY "TESTDB_DBTEST"."FECHA" ASC'
Tristan.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
Re: SQL Alchemy integration
On Wed, 2007-03-21 at 18:10 +, jbronn wrote: > > It's sleeping right now. The upcoming refactoring of Django's QuerySet > > mechanism looks like it'll make working with other ORMs a bit easier, > > so if someone wants to come back and revisit it then it'd be a bit > > less of an ambitious project ;) > > Is there any place (e.g. a trac page) where interested parties can > check out the progress on the QuerySet refactor? Since I recently > completed PostGIS integration for the GeoDjango branch (will be > committed to SVN branch pending Jeremy Dunck's approval), I have an > active interest in what you guys plan on doing in there. Not yet. I'll put up a wiki page when I get a chance. Haven't been working on this lately, since I've been putting my idle cycles into getting ready for 0.96. That seems to be settled now, so I can go back to this. Will try to get something up tomorrow or on the weekend. I assume you've read the original thread on this (http://groups.google.com/group/django-developers/browse_frm/thread/691da1d6e3b0661d/a52efdfd1bca037a?lnk=gst&q=QuerySet&rnum=1#a52efdfd1bca037a )? That describes the approach. The rough first pass that Honza Kral posted later in the thread is surprisingly close to what I've written as well. The actual implementation is really a two-pass process: first just a refactoring so that we split out the database-dependent bits into a Query set class that is used inside QuerySet, etc. This would be more or less bug-for-bug compatible with existing code (it might fix a bugs in passing; I'm not going to concern myself too much with not accidently fixing bugs). Pass two is then making sure we fix the couple of dozen open SQL generation bugs. This was really the motivation for the refactor, since it's currently very hard to tweak SQL generation (as you've no doubt noticed) in the current form. Hopefully you're also aware that Jeremy's and I have had a short discussion on this list (in the above thread, towards the end) about how to have the GIS fields generate the right SQL, since they're different from other fields. I'm still not completely in love with the solution we settled on, but I am aware of it, so I'll keep an eye on your branch as well to help make any transition easier. Anyway, like I said, since 0.96 is out the door, I'm going to ease back a little (not completely,obviously) from only fixing other peoples' problems and do some development work of my own and this is one of the things I'll be working on. > On a related note, Brian Beck has some implementation ideas on how > he'd go about integrating SQLAlchemy: > http://blog.case.edu/bmb12/2007/03/thinking_about_taking_over_the_djangosqlalchemy_branch Yeah, I saw that. Not sure I'd use exactly the approach he's advocating -- I suspect he's splitting off at too high a level, since there's not that much database dependency up at the model layer -- but it's not a bad way to approach the problem and certainly has the "working in increments" good feeling about it. Will be interesting to see what happens. Regards, Malcolm --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
