Skip to content

Clarify FLOAT/DOUBLE/REAL SQL types status in 2.1 beta release #728

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

Closed
Totktonada opened this issue Mar 1, 2019 · 0 comments
Closed

Clarify FLOAT/DOUBLE/REAL SQL types status in 2.1 beta release #728

Totktonada opened this issue Mar 1, 2019 · 0 comments
Assignees
Labels
sql [location] SQL manual

Comments

@Totktonada
Copy link
Member

We need to explicitly mention in the release notes for tarantool-2.1 that floating point SQL types are not planned to be compatible between 2.1 and 2.2 releases.

The reason of that is that in 2.1 we'll set 'number' format for columns of these types, but (likely) will restrict it to 'float32' and 'float64' in 2.2. The change of a format requires data migration and cannot be done automatically, because in 2.1 we have no information to distinguish 'number' columns (created from Lua) from FLOAT/DOUBLE/REAL ones (created from SQL).

Other types planned on 2.1 ( tarantool/tarantool#4019 ) seems to be more or less okay. Maybe it worth also to mention that VARCHAR(N) does not check a string length in 2.1 and we provide no guarantees on a behaviour in 2.2+ for strings that are not fit to the specified limit N.

@lenkis lenkis self-assigned this Mar 1, 2019
@lenkis lenkis added 2.1 sql [location] SQL manual labels Mar 1, 2019
@lenkis lenkis closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sql [location] SQL manual
Projects
None yet
Development

No branches or pull requests

2 participants