12 Commits

Author	SHA1	Message	Date
Jussi Saurio	d584a1879b	Mark WHERE terms as consumed instead of deleting them ... We've run into trouble in multiple places due to the fact that we delete terms from the where clause (e.g. when a constant condition is removed, or the term becomes part of an index seek key). A simpler solution is to add a flag indicating that the term is consumed (used), so that it is not translated in the main loop anymore when WHERE clause terms are evaluated.	2025-05-17 15:44:12 +03:00
Jussi Saurio	5e5788bdfe	Reduce allocations	2025-05-14 09:42:26 +03:00
Jussi Saurio	625cf005fd	Add some utilities to constraint related structs	2025-05-14 09:42:26 +03:00
Jussi Saurio	5386859b44	as_binary-components: simplify	2025-05-14 09:42:26 +03:00
Jussi Saurio	9d50446ffb	AccessMethod: simplify - get rid of AccessMethodKind as it can be derived	2025-05-14 09:42:26 +03:00
Jussi Saurio	52b28d3099	rename use_indexes to optimize_table_access	2025-05-14 09:42:26 +03:00
Jussi Saurio	d8218483a2	use_indexes: comments	2025-05-14 09:42:26 +03:00
Jussi Saurio	3442e4981d	remove some unnecessary parameters	2025-05-14 09:42:26 +03:00
Jussi Saurio	c18bb3cd14	rename	2025-05-14 09:42:26 +03:00
Jussi Saurio	c782616180	Refactor constraints so that WHERE clause is not needed in join reordering phase	2025-05-14 09:42:26 +03:00
Jussi Saurio	bd875e3876	optimizer module split	2025-05-14 09:42:26 +03:00
Jussi Saurio	ec45a92bac	move optimizer to its own directory	2025-05-14 09:42:26 +03:00