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
As a suggestion, instead of just using INT(8), INTEGER, FLOAT, DECIMAL data types, wouldn't it be better if it was rust data types for example u8, u16, u32, u64, i8, i16, i32, i64, f32, f64 for numeric data types?
As a suggestion, instead of just using INT(8), INTEGER, FLOAT, DECIMAL data types, wouldn't it be better if it was rust data types for example u8, u16, u32, u64, i8, i16, i32, i64, f32, f64 for numeric data types?
This is a reasonable point but for INT([size]) we will need to do some fancy logic to restrict sizes and as such will need a new type. For other things, we need to store the values in a way that allows us to do logic on them as if they are all the same thing.
This is why we use Value which, in the case of things like INTEGER -> I64 -> i64 does use rust's types; just wrapped into an enum.
Further:
Apologies for not seeing your issue earlier. I need to find a way to make it noted here but I have moved MultiSQL over to my GitLab instance and this repository (on GitHub) is just a mirror.
This is a reasonable point but for INT([size]) we will need to do some fancy logic to restrict sizes and as such will need a new type.
Ah right mate understood :)
For other things, we need to store the values in a way that allows us to do logic on them as if they are all the same thing.
This is why we use Value which, in the case of things like INTEGER -> I64 -> i64 does use rust's types; just wrapped into an enum.
Apologies for not seeing your issue earlier. I need to find a way to make it noted here but I have moved MultiSQL over to my GitLab instance and this repository (on GitHub) is just a mirror.
Activity
KyGost commentedon Jun 8, 2022
@Raj2032
Hi Raj, thanks for the questions.
This is a reasonable point but for
INT([size])we will need to do some fancy logic to restrict sizes and as such will need a new type. For other things, we need to store the values in a way that allows us to do logic on them as if they are all the same thing.This is why we use
Valuewhich, in the case of things likeINTEGER->I64->i64does use rust's types; just wrapped into an enum.Yup, we (I) use GlueSQL's:
https://discord.com/invite/C6TDEgzDzY
Further:
Apologies for not seeing your issue earlier. I need to find a way to make it noted here but I have moved MultiSQL over to my GitLab instance and this repository (on GitHub) is just a mirror.
Raj2032 commentedon Jun 8, 2022
@KyGost
:)
Ah right mate understood :)
Right I see mate.
Is MultiSQL similar to GlueSQL?
All good mate and thanks for letting me know =D
KyGost commentedon Jun 8, 2022
@Raj2032
They were originally the same and continue to share ambitions.
Raj2032 commentedon Jun 9, 2022
@KyGost Thanks mate :)
Raj2032 commentedon Jun 9, 2022
@KyGost Which one should I use though?
KyGost commentedon Jun 9, 2022
@Raj2032
Succinctly, briefly and incorrectly:
Raj2032 commentedon Jun 10, 2022
@KyGost Ah right thanks :)