- 23 Dec, 2014 14 commits
-
-
Mick Hansen committed
-
Mick Hansen committed
-
Mick Hansen committed
-
Mick Hansen committed
-
Mick Hansen committed
-
Mick Hansen committed
-
… options, closes #2012
Mick Hansen committed -
Mick Hansen committed
-
…by default since they are querying on primary key, closes #2698
Mick Hansen committed -
Mick Hansen committed
-
Mick Hansen committed
-
Mick Hansen committed
-
…ation.scope, closes #2740
Mick Hansen committed -
Mick Hansen committed
-
- 22 Dec, 2014 1 commit
-
-
clean and lint tests, enable jshint on tests
Mick Hansen committed
-
- 21 Dec, 2014 4 commits
-
-
Ran fixjsstlye on all the tests, fixed any outstanding errors, and enabled jshint for checking tests in continuous integration.
Matt Broadstone committed -
Mark migration logic as deprecated.
Mick Hansen committed -
add `.original` property to custom Error classes
Mick Hansen committed -
The current `.parent` property is a bit of a misnomer. `.original` better conveys the intent of the field and function of the class, which is to wrap the original database error. This commit does not remove the current `.parent` property for backwards compatibility.
Roman Shtylman committed
-
- 20 Dec, 2014 1 commit
-
-
This commit deprecates the migration logic from the sequelize core references the rewritten CLI and the new migration engine. Also this commit removes the respective migration tests.
Sascha Depold committed
-
- 17 Dec, 2014 6 commits
-
-
Resolving multiple hasMany cascades which weren't working in some cases
Jan Aagaard Meier committed -
… are not made for hooks:true #2746
Matheus Bratfisch committed -
…aints are not supported. #2736
Matheus Bratfisch committed -
Matheus Bratfisch committed
-
Matheus Bratfisch committed
-
Matheus Bratfisch committed
-
- 16 Dec, 2014 3 commits
-
-
Jan Aagaard Meier committed
-
Jan Aagaard Meier committed
-
linted and cleaned hooks.test.js
Jan Aagaard Meier committed
-
- 14 Dec, 2014 5 commits
-
-
Use ec2 instance in us-west-1
Mick Hansen committed -
Sequelize.close should close all connections once pool is being drained
Jan Aagaard Meier committed -
Dejan Ranisavljevic committed
-
Fixed a few misspelled words
Jan Aagaard Meier committed -
Brian Lundin committed
-
- 13 Dec, 2014 4 commits
-
-
Dejan Ranisavljevic committed
-
Dejan Ranisavljevic committed
-
Dejan Ranisavljevic committed
-
Sascha Depold committed
-
- 12 Dec, 2014 2 commits
-
-
Fixing "error: syntax error at or near ")"" when using upsert with postgres dialect
Jan Aagaard Meier committed -
When trying to insert values containing the character `)`, the RegEx is not modifying the string properly, throwing this error message: `error: syntax error at or near ")"`. Here's an example: Initial value: `VALUES ( \'Current Generator(s)\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\');` Current result: `SELECT \'Current Generator(s\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\');` Expected result: `SELECT \'Current Generator(s)\',\'CurrentGenerators__c\',NULL,NULL,\'Lead\',\'2014-12-10 22:31:24.076 +00:00\',\'2014-12-10 22:31:24.076 +00:00\';` This commit is removing the `replace()` method called. After reading the blog post referred, there's no explanation of why this need to be replaced - and it is working fine without it.
Jean-Philippe Monette committed
-