search

vocascan / vocascan-server

Server for Vocascan
https://vocascan.com
Apache License 2.0
26 stars 5 forks source link

No Database #98

Open Malta112 opened 1 year ago

Malta112 commented 1 year ago

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

luwol03 commented 1 year ago

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.

Malta112 commented 1 year ago

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 commented 1 year ago

image So .migrations is empty and i used npm

luwol03 commented 1 year ago

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 commented 1 year ago

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

Malta112 commented 1 year ago

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 commented 1 year ago

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