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

Some questions regarding this project #169

Open
Raj2032 opened this issue Jun 6, 2022 · 7 comments
Open

Some questions regarding this project #169

Raj2032 opened this issue Jun 6, 2022 · 7 comments

Comments

@Raj2032
Copy link

Raj2032 commented Jun 6, 2022

Hi I have some questions regarding this project:

  1. 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?
  2. Is there a Discord server for multisql?
@KyGost
Copy link
Member

KyGost commented Jun 8, 2022

@Raj2032

Hi I have some questions regarding this project:

Hi Raj, thanks for the questions.

  1. 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.

  1. Is there a Discord server for multisql?

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
Copy link
Author

Raj2032 commented Jun 8, 2022

@KyGost

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.

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.

Right I see mate.

Yup, we (I) use GlueSQL's:
https://discord.com/invite/C6TDEgzDzY

Is MultiSQL similar to GlueSQL?

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.

All good mate and thanks for letting me know =D

@KyGost
Copy link
Member

KyGost commented Jun 8, 2022

@Raj2032

Is MultiSQL similar to GlueSQL?

They were originally the same and continue to share ambitions.

@Raj2032
Copy link
Author

Raj2032 commented Jun 9, 2022

@KyGost Thanks mate :)

@Raj2032
Copy link
Author

Raj2032 commented Jun 9, 2022

@KyGost Which one should I use though?

@KyGost
Copy link
Member

KyGost commented Jun 9, 2022

@Raj2032

@KyGost Which one should I use though?

Succinctly, briefly and incorrectly:

  • Glue is more stable and refined.
  • Multi has more functionality.

@Raj2032
Copy link
Author

Raj2032 commented Jun 10, 2022

@KyGost Ah right thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants