Radosław Waśko 8c661fdb74 Database Joins (#4007) ... Implements https://www.pivotaltracker.com/story/show/184032869 # Important Notes - Currently we get failures in Full joins on Postgres which show a more serious problem - amending equality to ensure that `[NULL = NULL] == True` breaks hash/merge based indexing - so such joins will be extremely inefficient. All our joins currently rely on this notion of equality which will mean all of our DB joins will be extremely inefficient. - We need to find a solution that will support nulls and still work OK with indices (but after exploring a few approaches: `COALESCE(a = b, a IS NULL AND b is NULL)`, `a IS NOT DISTINCT FROM b`, `(a = b) OR (a IS NULL AND b is NULL)`; all of which did not work (they all result in `ERROR: FULL JOIN is only supported with merge-joinable or hash-joinable join conditions`) I'm less certain that it is possible. Alternatively, we may need to change the NULL semantics to align it with SQL - this seems like likely the simpler solution, allowing us to generate simple, reliable SQL - the NULL=NULL solution will be cornering us into nasty workarounds very dependent on the particular backend.		2023-01-05 10:36:22 +00:00
..
data	Adds Date, Time_Of_Day and Date_Time support to Excel IO (#3997)	2022-12-20 16:12:00 +00:00
scripts/postgresssl	Docker file for testing Postgres SSL and updated Postgres Spec (#3607)	2022-07-26 13:28:43 +00:00
src	Database Joins (#4007)	2023-01-05 10:36:22 +00:00
package.yaml	Simple CSV parser (#1268)	2020-11-05 16:53:50 +01:00