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

No Database #98

Open
Malta112 opened this issue Jun 21, 2023 · 7 comments
Open

No Database #98

Malta112 opened this issue Jun 21, 2023 · 7 comments
Assignees
Labels
kind/question Further information is requested

Comments

@Malta112
Copy link

No database because i dont know what is needet (Using mysql)

Expected behavior
Should be able to execute command to database but for example xyz.roles doesn't exist

Screenshots
image

Additional context
There was no step on how to create the database

@Malta112 Malta112 added the kind/bug Something isn't working label Jun 21, 2023
@luwol03
Copy link
Member

luwol03 commented Jun 21, 2023

Hello @Malta112,

can you please explain what you did that you got that error and how you attempted the install? And can you verify if the migrations already run by looking for any tables in your db. Especially there should be a table named .migrations, if so please post the records that are in there.

@luwol03 luwol03 added kind/question Further information is requested and removed kind/bug Something isn't working labels Jun 21, 2023
@Malta112
Copy link
Author

I Just followed the instructions to install the backend and there was never a way to create the database and i started the backend but it created only two strange tables:
image

@Malta112
Copy link
Author

image
So .migrations is empty
and i used npm

@luwol03
Copy link
Member

luwol03 commented Jun 21, 2023

Yes, they should be created automatically on start. Please show the full log if you run the server and please also provide some information how you run vocascan-server.

@Malta112
Copy link
Author

Im following the installation and running it by "pm2 start vocascan-server -- web"

@Malta112
Copy link
Author

GNU nano 6.2 vocascan.log.gz
info: migrating...
Executing (default): SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE' AND TABLE_NAME = '.migrations' AND TABLE_S>
Executing (default): SHOW INDEX FROM .migrations
Executing (default): SELECT name, createdAt, updatedAt FROM .migrations AS .migrations ORDER BY .migrations.name ASC;
info: ✓ migrating done in (93.873ms)
Executing (default): SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE' AND TABLE_NAME = '.seeders' AND TABLE_SCHE>
info: seeding...
Executing (default): SHOW INDEX FROM .seeders
Executing (default): SELECT name, createdAt, updatedAt FROM .seeders AS .seeders ORDER BY .seeders.name ASC;
info: ✓ seeding done in (9.39ms)
info: Server is running on port 5000.

@noctera
Copy link
Member

noctera commented Jun 21, 2023

Seems like the migrations are running perfectly.
@luwol03 might this be a mysql specific problem with any type of unknown name resolving? As far as I know we have never tested MySql explicitly, but I know that there might be some differences in the ORM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants