You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current solution has the following issue: We stored the subdomain as a denormalized column directly inside the baseUrls table. This, however, leads to the issue, that we now have multiple entries per baseUrl.
Will be solved by putting those subdomains in a simple separate table, which than can be joined with the baseUrl Table.
The text was updated successfully, but these errors were encountered:
As discussed today, we should shift this to the paths table, since there it does not hurt to store the denormalized data, and we do not need another join to compose the urls to download
This is still a denormalized column, however, otherwise we'd need
to do always an additional join on the "subdomains" table before we
can return the next entries to be downloaded.
[#21]
The current solution has the following issue: We stored the subdomain as a denormalized column directly inside the baseUrls table. This, however, leads to the issue, that we now have multiple entries per baseUrl.
Will be solved by putting those subdomains in a simple separate table, which than can be joined with the baseUrl Table.
The text was updated successfully, but these errors were encountered: