b04d9466ef
Merge https://github.com/jugglingdb/mysql-adapter
...
* https://github.com/jugglingdb/mysql-adapter :
Update README.md
Fixed typo in the require statement
0.0.1-6
Add checking for undefined in buildWhere
Fix injection
2013-06-13 09:41:35 -07:00
6bd48f5c2e
Merge branch 'master' of https://github.com/dgsan/mysql-adapter
...
* 'master' of https://github.com/dgsan/mysql-adapter :
Update imported.test.js
Conflicts:
test/imported.test.js
2013-06-13 09:40:59 -07:00
bcee504d77
Proper tests and support for connection collation/charset. Added semicov as a dev dependency because of how tests are run.
2013-06-13 09:34:31 -07:00
2c12977c13
Merge pull request #37 from dgsan/master
...
Fixing dumb import.
2013-06-12 16:12:11 -07:00
543f5de835
Update imported.test.js
...
Wrong method of calling.
2013-06-12 15:21:52 -07:00
87bf863a0a
Update README.md
...
Some initial documentation of `dataType` usage.
2013-06-06 12:25:20 -06:00
d086d0c845
Merge pull request #34 from dgsan/master
...
A couple additional unit tests using different dataTypes.
2013-06-06 10:17:25 -07:00
193e5d6463
Adds test that validate the basic behavior of numeric and date columns using the added recently added dataTypes.
2013-06-06 10:09:39 -07:00
3e90d39691
Merge pull request #33 from dgsan/master
...
Initial support of additional column types and connection collation/charset settings.
2013-06-04 15:01:43 -07:00
93e4898312
Update migration.test.js
...
Global leak error triggered because of missing var in line ported from coffeescript.
2013-06-04 15:58:17 -06:00
8b7ac18cc3
Support for local MySQL dataTypes via the dataType model field option.
...
Support for setting collation/charset at the schema level.
Porting of non-running migration test to new test running layout.
Resolves issue #19 . Resolves issue #28 . Resolves issue #17 .
Should allow for changing the types for particular columns (Int, SmallInt, BigInt, Text, Char, Float, etc.).
This seems to work with the current migration test, however use of floats and such in model instances has not been heavily tested.
Likewise, in porting migration the full suite of index migration tests has yet to be ported.
Likewise, issue with dropping columns from a model persists and seems related to `defineProperty` in JDB core choking when used to try and undefine.
2013-06-04 14:34:23 -07:00
7ffbb1f4a4
Merge pull request #32 from dgsan/master
...
Resolves #31 , #15
2013-05-30 13:51:11 -07:00
9291cbafdc
Resolves issues #31 , #15 .
2013-05-30 13:43:01 -07:00
141bf6394c
Merge pull request #29 from fallanic/master
...
Typo in require statement
2013-04-30 11:48:18 -07:00
efb8237819
Fixed typo in the require statement
2013-04-30 11:04:57 -07:00
4612ba275d
0.0.1-6
2013-04-22 08:41:41 +04:00
6c5666e23e
Add checking for undefined in buildWhere
2013-04-22 08:40:12 +04:00
400614a8c9
Fix injection
2013-04-18 22:58:21 +04:00
97e1b7eef0
Merge pull request #25 from dgsan/master
...
Fixes #21 , changes word for offset to 'skip' to match JDB core.
2013-04-18 09:13:08 -07:00
d7112909eb
Fixes #21
...
Changed param for using offset with limit to 'skip' so as to match JDB core.
(Unit test to be pushed to JDB core.)
2013-04-18 09:11:03 -07:00
a54dd29c43
Merge pull request #24 from dgsan/master
...
Since there's no timeout param to mocha test frequently fail somewhat randomly. Default timeout to 15000, which consistently passes on my system, whereas the default 2000 fails every time.
2013-04-18 08:43:05 -07:00
8921b54a1a
On slower systems the lack of a timeout argument to mocha makes some tests fail after 2 seconds.
...
At least on my rather sad dev box many mysql ops (particularly creating tables) can take quite a bit longer than 2 seconds. Accordingly I've added the moch '--timeout' parameter and set it to 15000, which seems to pass consistently on my dev box.
2013-04-18 08:35:56 -07:00
25b8cc8029
Merge pull request #23 from gierschv/master
...
Handle undefined when altering tables
2013-04-18 07:35:35 -07:00
fa617dc35f
Mistake in an undefined check
2013-04-18 15:57:56 +02:00
1bae8a8062
Handle undefined when altering tables
2013-04-18 13:20:05 +02:00
5f007eabc0
Ignore getSchema globa leak
2013-04-08 02:06:28 +04:00
e2d41d3dd3
Mass-runner friednly test
2013-04-08 02:00:16 +04:00
b6f0c2cfc8
Split test cases
2013-04-08 01:53:55 +04:00
cd3d2859cb
Added coverage to gitignore
2013-04-07 17:59:45 +04:00
ce6e7bf794
merge
2013-04-06 14:37:14 +04:00
e9eb9376fe
Handle undefined and boolean
2013-04-06 14:36:32 +04:00
de227f5f35
Merge pull request #16 from codebudo/master
...
Dependent JugglingDB version in package.json
2013-04-03 10:44:38 -07:00
8431ad4aef
Specify required jugglingdb version.
2013-04-03 10:39:05 -07:00
1f31c86169
0.0.1-5
2013-04-03 19:33:55 +04:00
f4a75f28c1
Upd node version for travis
2013-03-27 20:32:13 +04:00
cd0018f3a5
Upd test runner
2013-03-27 18:15:23 +04:00
4302a125ef
Fix undefined handling
2013-03-27 04:38:18 +04:00
9f063c13c5
Moved to mocha
2013-03-27 04:37:13 +04:00
f2b34378ae
FIx tests
2013-03-07 03:14:41 +08:00
70096afd1b
Upd package and README
2013-03-07 03:10:20 +08:00
cfdd519f32
Update package.json
2013-03-07 02:49:06 +07:00
5083c855a8
0.0.1-4
2013-02-22 01:26:13 +07:00
da973b56c9
Proper Point type registration
2013-02-22 01:25:15 +07:00
ec6d6e7572
Set User table name and fix test for migrations
2013-02-16 23:09:20 +08:00
b15aa88681
Made additional bug-fix changes as noted in comments previously, however while I'm fairly certain the changes are correct, not as sure about how to test. I kind of wonder if changing the USING clause even needs to be supported.
2013-02-14 14:05:49 -07:00
25202bd455
Semicolon consistency.
2013-02-14 09:52:00 -07:00
ac8f882175
This adds support for indexes to automigrate() and adds a check for the indexes existence to the migration.coffee 'should run migration' test.
...
All unit tests continue to pass. The code snippets for adding indexes are the declarative versions of the methods used in alterTable(), so the indexes should be consistant with previous declarations/additions.
Should resolve bug #5 .
As a side node, also removed the 'UNIQUE' clause from the `id` declaration as it is redundant with the 'PRIMARY KEY' declaration so far as I'm aware and results in what seems to be a second index getting maintained for no reason. (If I'm wrong about this I'd be intrested in the explanation. MySQL does have a lot of oddities.)
2013-02-14 09:37:32 -07:00
73807276bc
Updated deps
2013-02-12 17:10:15 +08:00
80cae2d14f
0.0.1-2
2013-02-10 05:07:15 +08:00
ad96800c64
Merge pull request #6 from zxqfox/patch-1
...
Fixup mistyped regexp
2013-02-06 00:17:24 -08:00
dgsan
dgsan
Anatoliy Chakkaev
Fabien Allanic
Vincent Giersch
S. Mikkel Wilson