On 12/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 1. Mark fields as optional.
> I don't like this because there will be lots of null values
> inserted into the database. I also don't think that this would be
> following SQL best practices.
Well, even in PHP you were going to have null columns. What you really
seem to want is a way to say, in SQL,
create table ticket (
user_id integer not null references "end_user" ('id') or references
"temp_user" ('id')
);
Except databases don't work that way ;)
So no matter what, you're going to get optional fields, with some
filled in for "real" users and NULL otherwise (and vice-versa).
Given that, optional fields seem to be the way to go. Use the admin,
train your staff on which fields need to be used in which situations,
and move on.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
