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

Proposal to Integrate Firebird Support into Apache ShardingSphere #33699

Open
makssent opened this issue Nov 17, 2024 · 7 comments · Fixed by #33773
Open

Proposal to Integrate Firebird Support into Apache ShardingSphere #33699

makssent opened this issue Nov 17, 2024 · 7 comments · Fixed by #33773

Comments

@makssent
Copy link
Contributor

Dear Apache ShardingSphere Community,

My name is Maxim, and I represent RedSoft, a software development company specializing in operating systems, database technologies, and enterprise solutions. We are currently developing a solution to integrate Firebird, a reliable and lightweight database system, with Apache ShardingSphere. I would like to discuss the possibility of merging our project into the main ShardingSphere repository.

Previously, the possibility of merging was discussed with one of your colleagues in one of the discussion sections. At that time, we planned to implement the basic Firebird functionality suitable for stable operation. We are now close to achieving this goal, which is why I am reaching out here. You can review our project by clicking on this link - link

Firebird is a trusted database system with a significant presence in regions like Eastern Europe and Latin America. By supporting Firebird, ShardingSphere can attract a new user base, particularly among organizations in industries such as finance, healthcare, and ERP systems, where Firebird is popular for its reliability and cost-effectiveness.

We welcome feedback and collaboration from the community to refine and perfect this contribution. This project can increase the value of both ShardingSphere and Firebird by providing users with more database options and expanding the project's reach to new industries and markets. We believe this will be beneficial for both sides

Thank you for considering this proposal. We look forward to your feedback and the opportunity to contribute to the ShardingSphere ecosystem.

Best regards,
Maxim
Software Engineer - RedSoft
LinkedIn: linkedin.com/in/maxim-igoshin
Telegram: @makssent
Email: maxim.igoshin@red-soft.ru

@terrymanu
Copy link
Member

It's great to hear this news; contributions from the community are always welcome.
I look forward to the integration of Firebird into the ShardingSphere master soon.

Don't hesitate to reach out with any questions you may have.

@makssent
Copy link
Contributor Author

That's wonderful! Then, during the next week, I'll clarify the necessary points with my team and get back to you with feedback.

@strongduanmu
Copy link
Member

This is really exciting news and more community users can benefit from it.

@strongduanmu
Copy link
Member

@makssent @TedCraft Thank you for your outstanding contribution. I have a suggestion, can we add subtasks to this issues? This will let the community know the progress of the issue so that developers who are interested can participate in it.

@makssent
Copy link
Contributor Author

Thank you as well for your cooperation. We will add the subtasks, but a little later =)

@TedCraft
Copy link
Contributor

I've added a few subtasks. In the near future we will also try to run tests for the parser to see which sql constructs are not working properly and/or are not supported. Is it better to create a separate parent subtask for parser related issues or add them to this issue?

@strongduanmu
Copy link
Member

I think we can add the adaptation of large feature modules to this issue. For each problem to be solved by each module, we can create an additional issue and link it here, for example:

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

Successfully merging a pull request may close this issue.

4 participants