Group Names Should NOT be Unique #7

New Issue

delvh · 2020-09-06T11:02:20+02:00

delvh commented

2020-09-06 11:02:20 +02:00

Describe the bug
If you create a Group that is named like another contact, you'll currently encounter a PSQLException because that name already exists.
The same thing happens, when a new user is created that is named like another one

Expected behavior
The first part can be easily fixed by moving the UniqueConstraint from Contact to User.
The second part is more challenging as it requires disallowing users to choose a name already present.
For the second part,

a String identifier (see #3) and
a system to prevent users from taking the same identifier is needed.

This was the stack trace after adding a Group test3 when another group already had that name:

**Describe the bug** If you create a Group that is named like another contact, you'll currently encounter a `PSQLException` because that name already exists. The same thing happens, when a new user is created that is named like another one **Expected behavior** The first part can be easily fixed by moving the `UniqueConstraint` from Contact to User. The second part is more challenging as it requires disallowing users to choose a name already present. For the second part, 1. a String identifier (see #3) and 2. a system to prevent users from taking the same identifier is needed. This was the stack trace after adding a Group `test3` when another group already had that name: ![grafik](/attachments/c7cfd77b-5728-4fd4-b032-c0cc491d0686)

grafik.png

81 KiB

delvh added this to the v0.2-beta milestone 2020-09-06 11:02:20 +02:00

delvh added the

bug

server

labels 2020-09-06 11:02:20 +02:00

kske changed title from ~~Group names should NOT be unique~~ to Group Names Should NOT be Unique

2020-09-06 11:25:58 +02:00

kske added the

L

label 2020-09-22 17:30:11 +02:00

delvh modified the milestone from v0.2-beta to v0.3-beta

2020-09-25 15:10:18 +02:00

kske commented

2020-10-20 17:47:43 +02:00

As previously discussed, I have a vision involving a major change of our data model, which whould take care of this and a few other issues.

Because I'm not certain if it will work as intended or how long it might take, the issue will not be solved straight away.

Still, I would like to try this out before finding an alternative solution and potentially wasting resources when the new data model is implemented afterwards.

As previously discussed, I have a vision involving a major change of our data model, which whould take care of this and a few other issues. Because I'm not certain if it will work as intended or how long it might take, the issue will not be solved straight away. Still, I would like to try this out before finding an alternative solution and potentially wasting resources when the new data model is implemented afterwards.

kske self-assigned this 2020-10-20 17:47:48 +02:00

kske added the

client

label 2020-10-20 17:48:06 +02:00

This repo is archived. You cannot comment on issues.