Skip to content

Conversation

@base698
Copy link

@base698 base698 commented May 13, 2013

No description provided.

zanamixx and others added 30 commits April 5, 2013 14:54
- coding style
- support both definition styles
- removing incomplete dataType check
- styling code more like the rest of the project
The auto-generated migrations don't mention done which is confusing if you're new to sequelize.
…en_async_update

Update the generated migration skeleton for async
Better error message for bad data types in define
…e to string concatenation. This has a large performance impact when doing many queries and having big result sets (attributesToSQL function)
…e to string concatenation. This has a large performance impact when doing many queries and having big result sets (attributesToSQL function)
…lum/sequelize into mysql-performance-improvements

Conflicts:
	lib/dialects/mysql/query-generator.js
…ents

Performance improvements for MySQL query generator
…/sequelize into mekanics-postgres-clause-order-fix
terraflubb and others added 29 commits May 10, 2013 15:04
In the MySQL dialect, values used to generate insert, bulk insert, and update queries are now checked for boolean-ness and will be turned into an int.

There was already duplicated logic applied to outgoing values to check if the value was a Date or not. I factored out value processing to a single function and added a check for typeof boolean.

The new function also escapes the return value since that was also being done everywhere.

Fixes sequelize#607
Still defaults to 'development' if NODE_ENV isn't set so backwards compatibility is ensured.
Also replaced one thrown error with a console.log. The rest of the errors were not thrown, and since this file is run from the shell, it will be an edge case that it will ever be caught. It looks messy when it happens. So it now returns an exit code of 1 to indicate things went sideways.
Because I always forget to add one to 'down' and then my migrations don't undo.

Also upgraded a ==.
And quit with a code after outputting it.
Make it possible to specify query options for find and findAll (specifically raw: true)
…tinyints

Properly process booleans in MySQL dialect to fix sequelize#607
thomascool added a commit that referenced this pull request Mar 21, 2014
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.