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

Add support for table name #2

Closed
adrians5j opened this issue Jan 10, 2018 · 2 comments
Closed

Add support for table name #2

adrians5j opened this issue Jan 10, 2018 · 2 comments
Assignees
Projects

Comments

@adrians5j
Copy link
Member

webiny-entity-mysql currently uses classId as a table name. It should be able to receive a custom table name (useful when users already have tables in an existing database).

@adrians5j adrians5j self-assigned this Jan 10, 2018
@SvenAlHamad
Copy link
Contributor

And table prefixes please :)

@adrians5j
Copy link
Member Author

@SvenAlHamad Support for table prefixes and custom table names added!

@Pavel910 Pavel910 added this to To Do in API via automation Jan 10, 2018
@Pavel910 Pavel910 moved this from To Do to Done in API Jan 10, 2018
Fsalker added a commit that referenced this issue Mar 4, 2020
Fsalker added a commit that referenced this issue Mar 9, 2020
…ave been wrapped inside /src/plugins. Package.json's name is updated according to {serviceName}. [WIP #1] The plugins used in src/plugins/index.ts are almost included in serverless.yml. [WIP #2] Yarn is run after the template is generated.
brunozoric added a commit that referenced this issue Oct 16, 2020
adrians5j added a commit that referenced this issue Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
API
  
Done
Development

No branches or pull requests

2 participants