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
4492: go/doltcore/env: Fix format logic for multi-database environments
4471: go/doltcore/actions: Sample CSV rows when inferring schema on import
4470: push docker image to dockerhub
Build Docker Image for dolt and push on every release
Dockerfile is WIP
4467: store/datas/pull: If the BPS is less than 1, report 0
^ prevents the push / pull progress reporter from reporting very small BP/s units.
4466: go: sqle: remotesrv: Successfully replicate CREATE DATABASE commands by instantiating new databases on the standby on demand.
4461: wrap spatial type string in single quotes when exporting
4458: Persist a commit mapping to the chunkstore after migration
The commit mapping is persisted as dangling chunks. We don't expect it to remain after a GC and it will not be picked up during a push or pull.
4449: integration-tests/go-sql-server-driver: Proof of concept a declarative approach to integration tests for sql-server interactions.
Converts bats/sql-server-config.bats to use a new approach.
1307: allow having node access to all tables in itself HAVING clause can reference column that is not in its select result or group by result (there can be no group by clause). These column references are from tables in HAVING node that it is not in its immediate children nodes.
1304: integration plan regressions
This PR addresses two problems:
Optimization rules that depend on pattern matching can fail to trigger with exchange nodes, which we failed to account for in testing. This fixes a small indexed join bug and runs integration query plans with parallelism = 2.
IndexedInSubqueryFilter should be prevented when the static side of the join takes a dependency on the index lookup. The check is now looser, and opaque nodes cannot disallow the transform. When we introduce subqueries that do reference outer scopes, we will need to be more careful and do deeper validation.
1303: adding support for st_area, st_perimeter, st_length
Only the Cartesian portion of these function is working, geodetic calculations are quite a bit harder.
I just throw an error for any unsupported functionality. st_area is calculated using shoelace formula.
Basic idea is to slice polygon into a bunch of triangles and sum up their areas. The function is not defined for polygons that intersect themselves, but from my testing it seems like MySQL returns the same values for these edge cases. st_perimeter is a NOT supported in MySQL, but it is in PostGIS (a postgres plugin for spatial types): https://postgis.net/docs/ST_Perimeter.html
Fix for: #4451
1301: Ensuring read-only check is executed for prepared and non-prepared statements
Quick fix for: #4434
Tested locally with a python script to verify that prepared statements to read-only dbs are now correctly blocked. After getting this fix out, we will follow up with more formal, automated test to cover this.
1293: no column reference can be made on dual table
Depends on dolthub/vitess#196
No GetField reference can be made on dual table. To differentiate between dual table and `dual` table(which can be created).
Dual table is constructed as ResolvedTable with empty table name and a single column with empty name in the parser.
Any column reference that becomes deferredColumn is replaced into alias that is present in projectedAliases in reorderProjection rule.
Any GetField column reference is not allowed on dual table.