Commit Graph

28 Commits

Author SHA1 Message Date
Raymond Feng 2a0970317a Rename ADL to LDL 2013-10-14 15:19:36 -07:00
Raymond Feng 9276025bc6 Refine the usage of rc 2013-08-23 14:31:43 -07:00
Raymond Feng 2b20ccdbd7 Use .loopback rc to load the config 2013-08-21 21:53:48 -07:00
Raymond Feng a06f4e5289 Disable console output for tests 2013-08-20 10:23:51 -07:00
Raymond Feng 9daf9ef91c Rename 'loopback-data' to 'loopback-datasource-juggler' 2013-07-30 14:21:10 -07:00
Raymond Feng 382f99b9c6 Rename schema/adapter to be dataSource/connector 2013-07-23 12:47:02 -07:00
Raymond Feng 4bedf2200c Add discovery test cases 2013-07-21 22:57:19 -07:00
Raymond Feng 9674a0308e Bring up the test cases 2013-07-21 17:27:54 -07:00
Raymond Feng 1329b40073 Start to add discovery 2013-07-20 23:38:40 -07:00
Raymond Feng 275405521b Migrate to loopback-data 2013-07-20 22:37:59 -07:00
dgsan 4bf7bcd2b3 After feedback changed Enum implementation to be a function.
The main side effect is that the `Enum` type can't be registered.
Use `EnumFactory()` to build an `Enum`.
2013-06-18 10:36:05 -07:00
dgsan c1616fd998 Support for Enum type in MySQL adapter. Requires patch to mainline JDB.
(See pull request: https://github.com/1602/jugglingdb/pull/296.)

After this there are several ways to use Enum with the adapter as shown in datatypes.test.js.
2013-06-17 14:25:57 -07:00
dgsan 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
dgsan 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
dgsan 543f5de835 Update imported.test.js
Wrong method of calling.
2013-06-12 15:21:52 -07:00
dgsan 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
dgsan 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
dgsan 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
Anatoliy Chakkaev e2d41d3dd3 Mass-runner friednly test 2013-04-08 02:00:16 +04:00
Anatoliy Chakkaev b6f0c2cfc8 Split test cases 2013-04-08 01:53:55 +04:00
Anatoliy Chakkaev cd0018f3a5 Upd test runner 2013-03-27 18:15:23 +04:00
Anatoliy Chakkaev 9f063c13c5 Moved to mocha 2013-03-27 04:37:13 +04:00
Anatoliy Chakkaev f2b34378ae FIx tests 2013-03-07 03:14:41 +08:00
Anatoliy Chakkaev cfdd519f32 Update package.json 2013-03-07 02:49:06 +07:00
Anatoliy Chakkaev ec6d6e7572 Set User table name and fix test for migrations 2013-02-16 23:09:20 +08:00
dgsan 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
Anatoliy Chakkaev e78fab6f5b Additonal test case 2012-12-15 00:09:42 +04:00
Anatoliy Chakkaev 2eed9a6e89 Init 2012-12-14 18:01:44 +04:00