Skip to content

Conversation

pyoner
Copy link
Contributor

@pyoner pyoner commented May 29, 2023

not completed
this PR breaks backwards compatibility

issue #71

pyoner added 14 commits May 29, 2023 09:46
…onsistency and readability

update(users.js): change foreign key constraint name from 'fk_roleId' to 'fk_role_id' to follow naming convention
… follow snake_case naming convention

refactor(user-api-tokens.js): change foreign key constraint name from fk_userId to fk_user_id to follow snake_case naming convention
…llow snake_case naming convention

refactor(users-emails.js): change primary key constraint name to follow snake_case naming convention
refactor(users-emails.js): change foreign key constraint name to follow snake_case naming convention
feat(users-emails.js): add verified column to track if email is verified or not
…to follow snake_case naming convention and improve readability

refactor(user-calculations.js): change foreign key constraint name from fk_userId to fk_user_id to follow snake_case naming convention and improve readability
…o follow snake_case naming convention and improve readability

refactor(user-datasources.js): change foreign key name from fk_userId to fk_user_id to follow snake_case naming convention and improve readability
…se for consistency and readability

feat(user-shared-collections.js): add foreign key constraint names for clarity and easier debugging
…rces table to snake_case for consistency and readability
…and readability

feat(logs.js): change trigger function to use new column name 'user_id' instead of 'userId' to match schema
…n users and users_emails tables to match database naming convention
@blokhin blokhin marked this pull request as draft May 29, 2023 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant