Hi, The normal user table will be synced from another application that doesn't allow non-real users. To support future integration, I need to ID's to be common across the two apps. The positive ID range is, in a sense, not available at this time. My real question was "is there any issue using negative IDs".
Take care, Michael. On Friday, November 4, 2016 at 8:37:30 AM UTC-7, Nate Granatir wrote: > > Or why not just assign certain Users to certain Groups? That seems like a > much more clean and simple way of handling the problem. You'd be able to > easily filter either set of users, and it would require very little custom > code. Plus, doing something like assigning negative IDs disguises what > you're actually trying to accomplish, whereas auto-assigning certain users, > to, say, a group called "Service Accounts", is perfectly clear to anyone > looking at the code. > > Nate > > On Wednesday, October 26, 2016 at 7:25:20 PM UTC-5, mic...@zanyblue.com > wrote: >> >> Hi, >> >> The Django contrib User model is used to create accounts in Django >> applications. I would like to keep accounts associated with real people >> separate from accounts created for mailing list and/or service accounts. I >> was planning on using negative ID's for these accounts and can't see any >> issue with this from a Django or DB point of view (would need to create and >> manage my own sequence for this). >> >> Can anyone see any issue with this? >> >> Take care, >> Michael. >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/395c3fd4-f3dc-48ca-a5cf-a38a78201f3d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
