Alyx

I did a quick test in a SSCCE running with mssql and the following code: ```typescript class User extends Model {} User.init({ firstName: 'VARCHAR(50)', }, { sequelize, }); await sequelize.sync({...

@nareshy-quisitive That part is tracked over here https://github.com/sequelize/sequelize/issues/9107 but we won't be able to do that until we have a proper non-n varchar type, which I opened a RFC for...

I haven't been able to replicate the problem. The issue in the OP isn't caused by Sequelize but by the infinitely recursing function. Without further data or an examples that...

I couldn't manage to reproduce a memory leak. I queries `/get` 3443 times, each time it returned 57 items. The memory usage fluctuated between 19MB and 35MB while the queries...

Unfortunately without a reproducible example there is no way for us to replicate your issue. We've tried multiple times in the past and are yet to find any evidence of...

Not the last time I ran it, the memory usage remained constant

If you want to implement this as a third party package, or in your own codebase: Writing a Data Type was greatly simplified in Sequelize 7, we have a guide...

That issue about prepared statements not being cleared is being tracked here: https://github.com/sequelize/sequelize/issues/10832, I'll post a status update over there

This was fixed in [Sequelize 7](https://sequelize.org/docs/v7/) ([pr](https://github.com/sequelize/sequelize/pull/15598)), but it is very unlikely we'll be able to backport the fix

None currently. Implementing a dialect adds a massive amount of maintenance work to the team so we only accept dialects that have a lot of demand. Right now there seems...