Sorry, it was my intention but had the wrong autocomplete. My apologies.
On Tue, May 28, 2013 at 10:00 PM, Angus Turner wrote:
> You'd be better off posting this to django-users as this list is for the
> development of django itself.
>
> Thanks
> Angus Turner
> angusisf...@gmail.com
>
>
> On Wed,
You'd be better off posting this to django-users as this list is for the
development of django itself.
Thanks
Angus Turner
angusisf...@gmail.com
On Wed, May 29, 2013 at 10:33 AM, Andres Osinski
wrote:
> Hi everyone, I've created a custom User model and reated a proxy for
> it, like this:
>
> cl
Hi everyone, I've created a custom User model and reated a proxy for
it, like this:
class User(AbstractUser):
USER_KINDS = (
('d', 'doctor'),
('p', 'patient')
)
kind = models.CharField(max_length=2, choices=USER_KINDS)
class DoctorManager(BaseUserManager):
def get
On Tue, May 28, 2013 at 2:26 AM, Anssi Kääriäinen
wrote:
> On 27 touko, 20:15, Shai Berger wrote:
> > On Monday 27 May 2013 19:37:55 Carl Meyer wrote:
> > I think a better solution for this is to keep the original method, and
> mark it
> > with skipUnless(is_core_db) -- we'd need to define is_cor
I have just run afoul of one of those "features that make no sense except
when combined with the test suite."In BaseDatabaseFeatures it looks
like this:
# Does the backend allow very long model names without error?
supports_long_model_names = True
What this flag actually does is (whe
