Community page update
The update for the community page doesnt seem to be working https://www.djangoproject.com/community/ -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Delete leads to IntegrityError (Trac Ticket #14896)
Hi all, I've tested the django 1.3 alpha release, but it seems that's the delete cascading rule doesn't work anymore when a class contains a ManyToManyField pointing on a class having subclasses. Consequently, I've created a ticket in django trac server (#14896) to describe my problem. Hope this one won't be unreviewed for a long period. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Specifying an order_with_respect_to for a self referential one to many relationship (still) fails
Hi all, I'd like to know if this problem, described in this post http://groups.google.com/group/django-updates/browse_thread/thread/e247ff8079eda192, will be solved in the next stable release of Django. Thanks. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Eclipse stack trace integration
Hey Russ Well it would be a nice addition to the Exception screen. On 3 mrt, 00:30, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Tue, Mar 2, 2010 at 10:00 PM, Thierry <thierryschellenb...@gmail.com> > wrote: > > Any idea how to make the file names in the stack trace clickable to > > open them in eclipse? > > > Symfony seems to do it: > >http://symfony-reloaded.org/tools > > > Quote: > > You can even click on any filename and Symfony will open your favorite > > IDE at the right line (if you use a supported IDE). > > Django-developers is for discussing the development of Django itself. > Unless you're proposing a specific change to Django to improve IDE > integration, you should direct your question to Django-users. > > Yours, > Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Eclipse stack trace integration
Any idea how to make the file names in the stack trace clickable to open them in eclipse? Symfony seems to do it: http://symfony-reloaded.org/tools Quote: You can even click on any filename and Symfony will open your favorite IDE at the right line (if you use a supported IDE). -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Django ORM and multidimensional data
Hi all, Have django developers planned the integration of new model fields capable to store multidimensional data ? If it's not the case, how can I submit this implementation request ? By implementing this kind of basic types, I think it could be a way for the Django project to reach the scientific community where Python and databases are more and more popular to store experimental and analyses data. Thanks, Thierry. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Subclassing models.Model to extend base functionalities and attributes
Hi everybody, Is there a way to subclass the 'models.Model' class behavior to extend base functionnalities and attributes to all classes contained in an application model ? It seems that the metaclass mechanism force the Python inheritance notation to a Database model inheritance. Thanks, Thierry. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Scaffolding
Ok scaffolding has seen a lot of ups and downs in the dev community. Type 1 "lets generate code, because that way our programming language sucks less" approach some PHP frameworks take. Type 2 Intelligent code snippets (generation) such as create_app Django needs more of the later. If i have a model, i would like to be able to generate: - 2 views (list, edit-detail-remove) - 2 templates - a modelform - the neccesary url config So I can start working from there, instead of starting from scratch. Symfony had this nicely worked out. Is there any django design convention which stops us from having a management command for this type of Scaffolding? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=.
Re: ORM roadmap
Thanks for your feedback. I appreciate it. I find an orm usefull for 3 scenarios: 1. - simple object retrieval posts.objects.all() 2. - performance optimized object retrieval, your raw approach would suffice here 3. - generating complex queries, and reusing sql components When you get to complex data models, Django currently fails on 2 and 3. Agreed though, I guess only a handful of apps encounter these problems. On Oct 4, 6:27 am, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Sun, Oct 4, 2009 at 5:00 AM, James Bennett <ubernost...@gmail.com> wrote: > > > On Sat, Oct 3, 2009 at 1:58 PM, Thierry <thierryschellenb...@gmail.com> > > wrote: > >> I know this is not a problem for most users. But when working with > >> complex projects or projects requiring some performance optimization > >> django orm doesn't suffice. Its a pity to see strong development on > >> django orm, while at the same time the sqlalchemy project has huge > >> traction. I currently run both orm's. The gap between sqlalchemy and > >> django orm is very large. Are there any plans to integrate sql > >> alchemy? > > > In a word, no. > > To put in one more voice of authority - speaking as a core developer, > I'm strongly opposed to modifying Django to use SQLAlchemy (or any > other external project for that matter) as the ORM. > > On top of the many valid reasons that James mentioned, there is one > more that I consider to be very important - one that stems from the > task that _any_ ORM is trying to perform. > > The goal of any SQL-backed ORM is to provide a syntax that makes it > easy to express SQL queries. The problem is, we already have a very > powerful, 100% feature complete syntax for expressing SQL queries - > it's called SQL. By very definition, _every_ SQL-backed ORM is > reinventing the wheel. > > ORMs have an important role to play in making the simple cases very > simple - and this is a sweet spot that Django's ORM, SQLAlchemy, and > any number of other ORM projects manage quite well. It is much easier > to write "Author.objects.all()" than to write "SELECT id, firstname, > lastname, birthdate, address1, address2, FROM author". > > However, this argument isn't about the simple cases - it is about the > complex cases. I will certainly grant that SQLAlchemy is certainly > able to cover more of the world of possible SQL queries than Django's > ORM. However, there are queries that even SQLAlchemy can't express (or > can't express elegantly). At this point, you can either continue > making modifications to your non-SQL language in an attempt to provide > 100% coverage of the SQL spec, or you can step back and say "No - we > already have a language that does this", and embrace it. > > Django has decided to take the latter approach. The recent proposals > for a raw() operator to make it easier to return Django model objects > as the result of a raw SQL query is an expression of this underlying > philosophical direction. > > So, no - for this reason, and many many others, we're not going to > adopt SQLAlchemy as Django's ORM. > > That said, we are committed to making it easier to use non-Django > components inside a Django project. If there is anything that we can > do to make it easier to use SQLAlchemy (or any other non-Django ORM) > inside a Django project, we're open to those suggestions. > > Yours, > Russ Magee %-) --~--~-~--~~~---~--~~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Custom fields and PostGreSQL composite types
Hello everybody, I'm working on a scientific project and Django has been chosen to develop our database model. I'd like to develop a 'PhysicalQuantityField' that manages a value and its relative unit. The first way to do this stuff is to translate the couple (value,unit) into a string and use Django custom field to manage the translation between Python and PostgreSQL. It works perfectly but I don't like the fact to mix the value and the unit. Moreover, postgres stores a string rather than a numeric and It makes me feel that the database model is not really clean. The second way, and in my mind the cleaner way, is to create a composite type at the postgres side called 'physicalquantity' with "CREATE TYPE physicalquantity AS (value numeric,unit varchar)". It is possible to add data to the database, but not to search data because the where clause of a select query, generated by a get or filter would be : (with measure as a composite type) SELECT measure FROM myapp_mytable WHERE measure = '(10,"mV")' That is incorrect. The correct query would be : SELECT measure FROM myapp_mytable WHERE (measure).value = 10 AND (measure).unit = 'mV' Can you tell me if there is a way to control the content of the where clause from the custom field class ? If not, do you think Django will be able one day to manage composite types ? Cordially, Thierry. --~--~-~--~~~---~--~~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
ORM roadmap
http://code.djangoproject.com/wiki/Version1.2Features I know this is not a problem for most users. But when working with complex projects or projects requiring some performance optimization django orm doesn't suffice. Its a pity to see strong development on django orm, while at the same time the sqlalchemy project has huge traction. I currently run both orm's. The gap between sqlalchemy and django orm is very large. Are there any plans to integrate sql alchemy? --~--~-~--~~~---~--~~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
order_with_respect_to fail
Hi !
I got some errors by using the Meta options order_with_respect_to:
class Category(PublicationBase, LocalisationBase):
ITEM_PER_PAGE = 12
name = models.CharField(max_length=255)
pictogram = models.ImageField(upload_to="categories", blank=True)
old_id = models.PositiveIntegerField(blank=True)
parent = models.ForeignKey("Category", blank=True, null=True)
class Meta:
ordering = ['name']
order_with_respect_to = 'parent'
def __unicode__(self):
return self.name
I post on django-users. I got some email from many django users who
whant to know if I found a workaround.
I found this ticket: http://code.djangoproject.com/ticket/2740 but I
don't like to patch django.
Here is my post on django-users:
http://groups.google.com/group/django-users/browse_thread/thread/1374d256a91393c9/6b5391721a656adc?lnk=gst=order_with_respect_to+fail+any+workaround#6b5391721a656adc
I know you work really hard for us, but can I know if the bug will be
corrected shortly or not. With this information I I can take the
decision of patching or not django.
Regards,
Thierry
--~--~-~--~~~---~--~~
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
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
Re: auto_now_add and auto_now
On 13 oct, 17:15, Brian Beck <[EMAIL PROTECTED]> wrote: > On Oct 13, 8:38 am, "Mike Scott" <[EMAIL PROTECTED]> wrote: > > > Secondly this question has been asked, and solved many times. If you search > > through the django-users archives I'm sure you'll find plenty of solutions. > > There are solutions out and about in the blogosphere too. > > Actually I think this is an appropriate place to ask since the > resolution (which was unclear) never resulted in action. I was > confused about these myself just yesterday because the documentation > doesn't mention anything about possible future deprecation. The only > action was three months ago with a DeprecationWarning patch that isn't > checked in. Thanks Brian, that why I ask here, I was really confused. Thierry. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
