RE: Creating seperate unique ids within the same table

lf Of Andrew Pinkham Sent: Monday, October 22, 2018 11:51 AM To: django-users@googlegroups.com Subject: Re: Creating seperate unique ids within the same table On Oct 22, 2018, at 12:29, Matthew Pava wrote: > I am curious why you think it is anti-practice to expose primary keys for > user-visib

Re: Creating seperate unique ids within the same table

Joel said this was a requirement: One of the important criteria I had was that these IDs should be easily memorable. Unfortunately UUIDs are not memorable, being too long to remember. A primary key that appears in a URL is just an implementation detail - the implementation could change, and

Re: Creating seperate unique ids within the same table

On Oct 22, 2018, at 12:29, Matthew Pava wrote: > I am curious why you think it is anti-practice to expose primary keys for > user-visible purposes. > My URLs all have the PK to the object in them, and any advanced user would be > able to “reverse engineer” a URL if they guess the PK of an object

RE: Creating seperate unique ids within the same table

the PK in the URL of an object. I’m just curious. From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of bill.torcaso.ox...@gmail.com Sent: Monday, October 22, 2018 10:20 AM To: Django users Subject: Re: Creating seperate unique ids within the same table Joel, I

Re: Creating seperate unique ids within the same table

Joel, I completely agree that UUIDs are not memorable. I still think you would be well-served to make a UUID the basis for uniquely defining a person. If you want to further add a short name, you could make an object class that has a UUID and, say, an 8-digit number. If you assert that the

Re: Creating seperate unique ids within the same table

Thank you Bill. I had a look at UUIDs. One of the important criteria I had was that these IDs should be easily memorable. Unfortunately UUIDs are not memorable, being too long to remember. :( Sincerely yours, Joel G Mathew On Mon, 22 Oct 2018 at 19:40, wrote: > > Hello all, > > The previous di

Re: Creating seperate unique ids within the same table

Hello all, The previous discussion shows a method that will work. but I think it has disadvantages, and I want to suggest another approach. The disadvantage of using a primary key from a table, any table, is that you are committing to that table and that primary key for all eternity. this

Re: Creating seperate unique ids within the same table

ober 18, 2018 9:19 AM > To: django-users@googlegroups.com > Subject: Re: Creating seperate unique ids within the same table > > Hi Matthew, > Yes, and I am using the id field to query the database for many operations. > But I do not want to share this id to the patient. The reason is t

RE: Creating seperate unique ids within the same table

- From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Joel Mathew Sent: Thursday, October 18, 2018 9:19 AM To: django-users@googlegroups.com Subject: Re: Creating seperate unique ids within the same table Hi Matthew, Yes, and I am using the id field to query th

Re: Creating seperate unique ids within the same table

Joel Mathew > Sent: Wednesday, October 17, 2018 10:41 PM > To: django-users@googlegroups.com > Subject: Re: Creating seperate unique ids within the same table > > Hi Phako, > Thank you. I'm already following this practise. I have the following > additional Mod

RE: Creating seperate unique ids within the same table

eckin? -Original Message- From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Joel Mathew Sent: Wednesday, October 17, 2018 10:41 PM To: django-users@googlegroups.com Subject: Re: Creating seperate unique ids within the same table Hi Phako, Thank you. I'

Re: Creating seperate unique ids within the same table

ty that is calculated each time based on >> the count of patients in the clinic. >> >> >> >> From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] >> On Behalf Of Joel Mathew >> Sent: Wednesday, October 17, 2018 11:01 AM >>

Re: Creating seperate unique ids within the same table

gt; >> From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] >> On Behalf Of Joel Mathew >> Sent: Wednesday, October 17, 2018 11:01 AM >> To: django-users@googlegroups.com >> Subject: Creating seperate unique ids within the same table >> &

Re: Creating seperate unique ids within the same table

legroups.com [mailto: > django-users@googlegroups.com] *On Behalf Of *Joel Mathew > *Sent:* Wednesday, October 17, 2018 11:01 AM > *To:* django-users@googlegroups.com > *Subject:* Creating seperate unique ids within the same table > > > > I have an application which is a clinic m

RE: Creating seperate unique ids within the same table

patients in the clinic. From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Joel Mathew Sent: Wednesday, October 17, 2018 11:01 AM To: django-users@googlegroups.com Subject: Creating seperate unique ids within the same table I have an application which is a

Creating seperate unique ids within the same table

I have an application which is a clinic management software which allows login into different clinics, and needs to keep patient records of each clinic seperately. The patient records are filed in one common model, with a ForeignKey referring to the clinic to which a patient belongs. Hitherto I ha