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

Improvement in Ballerina Persist documentation #8688

Open
shayanmalinda opened this issue Feb 15, 2024 · 2 comments
Open

Improvement in Ballerina Persist documentation #8688

shayanmalinda opened this issue Feb 15, 2024 · 2 comments
Assignees
Labels
Category/Content All written content related issues (Technical content, english language etc) Type/Improvement Improvements required on the website.

Comments

@shayanmalinda
Copy link

shayanmalinda commented Feb 15, 2024

Description

I was trying to use Bal persist by pointing out to a MySQL database.
I was referring below documentation and it says that

Along with the bal persist init command, you can specify the datastore that you are going to use in the application and also the module that you need to add the generated code to. Both these parameters are optional. If you don’t provide them, the datastore will be set to inmemory, and the module will be set to root module by default.

https://ballerina.io/learn/manage-data-persistence-with-bal-persist/

But this doesn't mention how I can specify the datastore.
It will be better if we can include that step in this documentation.

Related website/documentation area

Add/Uncomment the relevant area label out of the following.

@shayanmalinda shayanmalinda added the Type/Improvement Improvements required on the website. label Feb 15, 2024
@TharmiganK
Copy link
Contributor

There should be link to this page: https://ballerina.io/learn/supported-data-stores/
@daneshk @sahanHe FYI

@anupama-pathirage
Copy link
Contributor

@daneshk any update on this? Please get this fixed asap.

@anupama-pathirage anupama-pathirage added the Category/Content All written content related issues (Technical content, english language etc) label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category/Content All written content related issues (Technical content, english language etc) Type/Improvement Improvements required on the website.
Projects
None yet
Development

No branches or pull requests

5 participants