mysql2 | A modern , simple and very fast Mysql library for Ruby

Your lock file contains conflicting dependencies. Since you were able to reproduce the error locally using npm ci we have a good way to test a fix locally.

It looks like you are depending directly on React 16. Is that something that you need directly, or is it just a dependency for Next.js?

If it's not something you need directly, upgrade it per the Next.js docs:

the service is now returning a promise, and it's also handling response instead of controller.

to return from service, you need to promisify service: return a promise which resolves when you get db data, or on error, and then you also need to await the service, which it's wrapped in try/catch for error handling.

once it's all done, handle response from the controller:

service:

The RDS proxy sits between your application and the database & should not result in any application change other than using the proxy endpoint.

Should I close the connection after executing my queries or leave it open for the RDS Proxy to handle?

You should not leave database connections open regardless of if you use or don't use a database proxy.

Connections are a limited and relatively expensive resource.

The rule of thumb is to open connections as late as possible & close DB connections as soon as possible. Connections that are not explicitly closed might not be added or returned to the pool. Closing database connections is being a good database client.

Keep DB resources tied up with many open connections & you'll find yourself needing more vCPUs for your DB instance which then results in a higher RDS proxy price tag.

And if I should close the connection, then what's the point of using an RDS Proxy in the first place?

The point is that your Amazon RDS Proxy instance maintains a pool of established connections to your RDS database instances for you - it sits between your application and your RDS database.

The proxy is not responsible for closing local connections that you make nor should it be.

It is responsible for helping by managing connection multiplexing/pooling & sharing automatically for applications that need it.

An example of an application that needs it is clearly mentioned in the AWS docs:

Many applications, including those built on modern serverless architectures, can have a large number of open connections to the database server, and may open and close database connections at a high rate, exhausting database memory and compute resources.

To prevent any doubt, also feel free to check out an AWS-provided example that closes connections here (linked to from docs), or another one in the AWS Compute Blog here.

You should not store an array of foreign keys. That's not a valid relational data design.

The relationship between products and colors in your database is many-to-many, and any such relationship is best stored in a third table:

You're need to target the correct table and use LIKE instead of =.

You can use ERB markup in the database.yml file, which lets you use an environment variable here. In general I'd suggest making default values for things be whatever default will work in a plain non-Docker development environment.

MySQL limits which statements can be done in prepared statements, start transaction is not allowed. See SQL Syntax Allowed In Prepared Statements and here is a demonstration.

execute is always using and caching prepared statements. This is good if the query is complex (MySQL doesn't have to parse it every time) or takes arguments (for security).

However, if your query is simple and does not take any arguments there's no need to prepare it. Use query which just runs the SQL. This both avoids the error you're getting, and it avoids filling up the prepared statement cache.

Yes i got it Gemfile in 13th line must be written like this and check for ownershhip of TMP folder

gem "mimemagic"

Seems that a column name in you import files is not valid as you see at the end of you error message you have