Proposal for Scribe-Server

[axif0]

Terms

• I have searched open and closed feature requests
• I agree to follow Scribe-Server's Code of Conduct

Description

For downstream application like Scribe-Android, Scribe-IOS, Scribe-Desktop or Scribe-web, Scribe-server plays a major role to pass the data from Scribe-Data. To make this transaction happen, we need to

1. Populate sqlite files Scribe-Data or create a workflow, that run and update sqlite files periodically.

2. Rename the sqlite file like {iso}_{lang}_langdb.sqlite, so that we can get iso and lang. And can save them in MariaDB in Scribe_server_details table.
   

3. We need to first make migration first. Sqlite to MariaDB. We need to install these library to make the migration happen.

   • go get github.com/go-sql-driver/mysql
   • go get github.com/mattn/go-sqlite3

Using make migrate we can able to start the transaction, We also need threading, as it takes good amount of time we need to use files in parallel.

In server it saves like these-

4. Using mysqldump -h localhost -P 3306 -u root -p --no-data scribe_server > db/schema/schema.sql to generate schema. which covers > Create the database schema for Scribe-Server #19

5. In query.sql we need to write the queries.

6. Using make generate-db' cmd db.go,models.goandquery.sql.go` will be created.

   

7. And routing logic will be after that.

CC: @wkyoshida , @andrewtavis , @henrikth93

This is my understanding of Scribe-Server so far. Am I on the right track? Your suggestions would be really helpful! 😊

Contribution

No response

[andrewtavis]

Parts of this look really promising, @axif0! Would we be able to have a schema within MariaDB that then would allow us to have tables like german.nouns, german.adjectives, etc? I guess I'm a bit confused why we'd need to have the language and the ISO in the DB as whatever access method we're using could potentially have an ISO to language name conversion.

Thanks for opening this discussion! Looking forward to figuring all this out 💙😊

[axif0]

Would we be able to have a schema within MariaDB that then would allow us to have tables like german.nouns, german.adjectives, etc?

As far as I know, we can't. Will also talked about this in this discussion

I guess I'm a bit confused why we'd need to have the language and the ISO in the DB as whatever access method we're using could potentially have an ISO to language name conversion.

Actually to get a language full name along with ISO, we need to get the language_metadata in Scribe-Data. My idea is if we put those in the file name we don't need language_metadata. How do we optimize this actually?

[andrewtavis]

Ah thanks for pointing out the comment! Makes sense :) I still think we don't need to do both the ISO and the language name. I'm just wondering where there are cases where we need both and can't get the other from the end application. We can code a conversion into Scribe-iOS or Scribe-Android if need be.

I think we can do a german.sqlite -> German MariaDB tables, and then we'll have language name based tables, and in the end applications we'd query the new data based on the language name that we can convert to if need be. Where would we need to have the ISO in this situation? Just checking all this! 😊

[axif0]

We can code a conversion into Scribe-iOS or Scribe-Android if need be.

Actually I found route for /languages previously in openapi to get all languages.

Should we skip for that now?

[andrewtavis]

Ya it seems like it wouldn't be needed :)

[andrewtavis]

Is there anything else that's needed here, @axif0? Feel free to close if we're all done here 😊

[axif0]

Is there anything else that's needed here, @axif0? Feel free to close if we're all done here 😊

Ya, looks like it's done 😅

[andrewtavis]

Closing it up then :) Thanks much, @axif0! 😊