On Sun, 2009-01-18 at 10:59 -0800, phoebebright wrote:
> Got django reading the view ok. Potential problem where table uses two
> fields as a primary key - don't think django likes this, but think I
> can use a view to get around this one too.
Yes, we don't support multi-column primary keys at
Got django reading the view ok. Potential problem where table uses two
fields as a primary key - don't think django likes this, but think I
can use a view to get around this one too.
On Jan 17, 1:59 pm, phoebebright wrote:
> That sounds like a very useful feature -
That sounds like a very useful feature - gets my vote.
Will have another go at getting django to read a view with mysql -
could well be a silly error of mine causing the problem.
On Jan 17, 10:47 am, Malcolm Tredinnick
wrote:
> On Sat, 2009-01-17 at 02:14 -0800,
On Sat, 2009-01-17 at 02:14 -0800, phoebebright wrote:
> I say an earlier post that seemed to imply they did.
>
> I created a view in an existing db and wrote a model test to match it
> so syncdb works fine.
Hm ... it just occurred to me: whilst running syncdb probably works if
you've specified
On Sat, 2009-01-17 at 02:14 -0800, phoebebright wrote:
> I say an earlier post that seemed to imply they did.
Well, for reasonable values of "works", that's true. There's no special
view handling code in Django, but, particularly for read-only code, they
should work without any problem. You can
I say an earlier post that seemed to imply they did.
I created a view in an existing db and wrote a model test to match it
so syncdb works fine.
But when I try to import it I get:
ViewDoesNotExist: Could not import todo.views. Error was: cannot
import name test
The ability to use views would
6 matches
Mail list logo