Thanks to everyone who posted suggestions to help with our problem of
duplications. In the end, we simply deleted the few duplicate resource
records using the web user interface: there weren't as many duplicates as I
first thought.
That left the duplicate resource-to-resource link records, of
Thanks, Martha, that will be useful!
David
On Tuesday, 25 February 2020 19:07:01 UTC, Martha S wrote:
>
> I installed DBeaver Community Edition (https://dbeaver.io/) to generate
> an ERD. Here is a copy I just exported to PNG and converted to PDF. I hope
> it helps.
>
> Martha
>
> On Monday,
Hi David,
I don't really have an ERD available, although someone on our team might.
I'll ask around.
-Alexei
Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
On Mon, Feb 24, 2020 at 1:21 AM Andrew Jones <
andrew.jo...@historicengland.org.uk> wrote:
> I would recommend
I would recommend that you use the django model to delete the resources.
Like you, we were not confident that we knew enough about the database
structure to confidently execute SQL without leaving various elements all
over the place. You also need to update the index etc.
I would write a
Hi Alexei
Thank you for the details. I should have asked about doing this using SQL,
which seems the more obvious way of doing it but I had looked at the
database structure and couldn't see how it related to the data models. Is
there anything for developers such as an entity relationship
Hi David,
There isn't a baked in "grep"-like command to do what you want but I've
crafted a bit of sql that you might be able to run to retrieve resource
instances based on node values.
SELECT t.tileid,
t.resourceinstanceid,
t.tiledata,
n.nodeid
FROM tiles t
LEFT JOIN nodes n ON t.nodegroupid =
