MySQL2 warning: "invalid configuration option"

My logs are flooded with

Ignoring invalid configuration option passed to Connection: supportBigNumber. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration option to a Connection

Happens every time I make a db request. Running MySQL 8.

How to fix this? Even if I can ignore it, it creates some noise.

Did you ever figure this out? I’m getting the same thing.

What database are you connecting to and where do you see this error?
What settings have you set in your db connection dialog?

I am connecting to a dev db I made in a Digital Ocean cluster. I see it when selecting the Development target.

and I’m not sure where to find my connection dialog. Are you referring to my target in project settings?

For me it’s on my local MySQL 8 when running Wappler Node Projects.
(Default config, nothing customized)

See

where root or username should be changed to user.

Ben, that’s a different issue / error and it’s already user in our scripts.

1 Like

Bumping this. I’m running hosted mySQL on DO and am experiencing this as well

Any advice?

This is a heads-up warning for future MySQL2 versions. Currently, it can be safely ignored.

This is now fixed in the latest Wappler 6.2

1 Like

This topic was automatically closed after 20 hours. New replies are no longer allowed.