Timeline for ArcSDE PostgreSQL mixed environment error connecting to schemas
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2017 at 15:52 | vote | accept | ziggy | ||
| Sep 26, 2017 at 15:51 | history | edited | ziggy | CC BY-SA 3.0 |
added 384 characters in body
|
| Sep 24, 2017 at 22:51 | answer | added | pauldzy | timeline score: 0 | |
| Sep 18, 2017 at 19:37 | history | tweeted | twitter.com/StackGIS/status/909864030688497665 | ||
| Sep 16, 2017 at 15:40 | comment | added | ziggy | database security for this specific setup is not a main concern of mine, I am aiming for a neat and ordered working database where I can do my SQL in the backend and have my coworker use ESRI tools | |
| Sep 16, 2017 at 15:38 | comment | added | ziggy | yes Vince I intentionally created this "antipattern" because to me (even though I am a newby in the DBMS world)it does not make sense to store all 200+ tables of mine in one massive database schema. They should be broken up by classification. so I am trying to experiment with this setup that would be more advantageous for me and my colleagues searching for tables and using them. | |
| Sep 16, 2017 at 15:11 | answer | added | Regina Obe | timeline score: 1 | |
| Sep 15, 2017 at 23:45 | history | edited | Vince | CC BY-SA 3.0 |
English usage; naming
|
| Sep 15, 2017 at 23:40 | comment | added | Vince |
Yes, this is so wrong, you've created a new antipattern, and destroyed the integrity of your geodatabase in the process. It's time to start over from scratch in a new database. You can choose to follow best practice within the requirements of enterprise geodatabase operation, or you can choose your "unconventional" paradigm, without a geodatabase (and in violation of all rules about database security). If you choose EGDB, be certain that you NEVER load data as the sde login, and NEVER change the schema of any table registered with the geodatabase.
|
|
| Sep 15, 2017 at 18:51 | history | edited | ziggy | CC BY-SA 3.0 |
added 92 characters in body
|
| Sep 15, 2017 at 18:50 | comment | added | ziggy | no now nobody can connect specifically to those schemas (but we all can use the sde role...), il update that in my Q | |
| Sep 15, 2017 at 18:49 | comment | added | Midavalo♦ | So your colleagues can still access those tables, but you can no longer access them? Is it only when your colleagues are access the tables? Is that error in ArcGIS or something else? | |
| Sep 15, 2017 at 18:36 | history | edited | ziggy | CC BY-SA 3.0 |
added 83 characters in body
|
| Sep 15, 2017 at 18:29 | history | asked | ziggy | CC BY-SA 3.0 |