Extended table relations

ure if this solution is a good one and I feel that there must be a better way to do that in Django. How should I approach those two issues? Thanks, Zbigniew Braniecki -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this

Re: multi-db and ForeignKey

On Jan 8, 1:33 am, Russell Keith-Magee wrote: > This is a known limitation, and there are plans to add this - or at > least, to provide a workaround  - for 1.2 final. There have been some > recent django-dev discussions if you want to see the state of our > thinking on the problem. The short vers

multi-db and ForeignKey

I'm experimenting with multi-db and it fits perfectly some major projects I'm working on. Man, I wish it was in django 1.1! :) Anyway, one issue I found that limits the scope of multi-db use is the ForeignKey constrain. It seems impossible to create a model that references another model from anoth

Re: Multiple vhosts in one django project

Or maybe I should use separate projects for docs.slownik.pl and www.slownik.pl. The problem is that they share a lot of data so I'd need to have three DB's: - models specific to docs.slownik.pl - models specific to www.slownik.pl - models shared between those two projects The first two are done

Re: Multiple vhosts in one django project

> They share data but have separate databases? They share some data, but they have their own models. For example Library and Bookstore may share models like Book, Author, ISBN, list of countries and locales in which the book could be published in. But they also have their custom models, Library

Multiple vhosts in one django project

I'm trying to set up a web project that will use multiple vhosts. In particular, I have a project called "slownik" and a domain "slownik.pl". Now, there are several apps in this project: - browser, docs, api. They share the same data, but they are different "views". Now, the common way in django

Re: Admin view - merge two tables? (potentially bad db design)

y Question.objects.get('x') or Question.objects.filter() or Question.objects.all() they are already joined with QuestionProperties values? Thanks! Zbigniew Braniecki --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Dja

Admin view - merge two tables? (potentially bad db design)

I'm working on an experimental survey application. It's supposed to be very flexible and expendable to allow creation of various kinds of surveys. One of the challenges I met is that custom forum may want to have custom fields and I would like to avoid having to add a new field to Question for a