Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make date handling more in-line with MySQL #4

Merged
merged 1 commit into from Sep 2, 2016

Conversation

LinuxJedi
Copy link
Contributor

Date limit of year 1400 was used due to Boost's limits.

This patch strips out the use of Boost for date handling and sets the
lower limit to year 1000.

Date limit of year 1400 was used due to Boost's limits.

This patch strips out the use of Boost for date handling and sets the
lower limit to year 1000.
@davidhall586 davidhall586 merged commit 1a7883f into mariadb-corporation:develop Sep 2, 2016
drrtuy referenced this pull request in drrtuy/mariadb-columnstore-engine Dec 11, 2018
LinuxJedi added a commit to LinuxJedi/mariadb-columnstore-engine that referenced this pull request Feb 6, 2020
When ALTER TABLE ... ENGINE= is called the following happens:

1. A temporary table is created in the new engine with the real table
   name but a temporary file name supplied
2. A bulk insert is started from old to new table
3. The old table is dropped
4. The new table is renamed

For mariadb-corporation#1 we use the real table name instead of the temporary file name
(otherwise step mariadb-corporation#2 breaks), we were therefore trying to skip mariadb-corporation#4.
This broke regular RENAME TABLE commands.

With this patch we detect if the rename is for a temporary to real table
and skip it. Since this is the only instance where we support temporary
tables.

This patch also fixes issues with extracting table names from file
names and some other irrelevant stuff.

Longer term if we want to support temporary tables we need to store the
provided filename in our metadata since it could be different from table
name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants