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
e109adc737
Merge pull request #41 from gierschv/fix-boolean
...
Fixes boolean conversion when fetching data from database
2013-06-28 11:46:37 -07:00
Vincent Giersch
6fa023250b
Fixes boolean conversion when fetching data from database
2013-06-28 17:44:12 +01:00
Vincent Giersch
b91d2cf241
Fixes variable name
2013-06-28 17:34:25 +01: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
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
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
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
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
dgsan
7ffbb1f4a4
Merge pull request #32 from dgsan/master
...
Resolves #31 , #15
2013-05-30 13:51:11 -07:00
dgsan
9291cbafdc
Resolves issues #31 , #15 .
2013-05-30 13:43:01 -07:00
Anatoliy Chakkaev
6c5666e23e
Add checking for undefined in buildWhere
2013-04-22 08:40:12 +04:00
Anatoliy Chakkaev
400614a8c9
Fix injection
2013-04-18 22:58:21 +04:00
dgsan
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
Vincent Giersch
fa617dc35f
Mistake in an undefined check
2013-04-18 15:57:56 +02:00
Vincent Giersch
1bae8a8062
Handle undefined when altering tables
2013-04-18 13:20:05 +02:00
Anatoliy Chakkaev
e9eb9376fe
Handle undefined and boolean
2013-04-06 14:36:32 +04:00
Anatoliy Chakkaev
4302a125ef
Fix undefined handling
2013-03-27 04:38:18 +04:00
Anatoliy Chakkaev
da973b56c9
Proper Point type registration
2013-02-22 01:25:15 +07:00
dgsan
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
dgsan
25202bd455
Semicolon consistency.
2013-02-14 09:52:00 -07: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
Alex Yaroshevich
5a7a30acdd
Fixup mistyped regexp
...
There is no «Unknown database 'dbname'» but «ER_BAD_DB_ERROR: Unknown database 'dbname'»
2013-02-04 06:03:46 +04:00
Anatoliy Chakkaev
035a8e8bac
Merge branch 'master' of github.com:1602/jugglingdb-mysql
2013-01-30 22:17:12 +07:00
Anatoliy Chakkaev
718b7fd320
Specify adapter name
2013-01-30 22:15:32 +07:00
Anatoliy Chakkaev
65a0baa633
Listen for error on connection, close #4
2013-01-30 22:15:18 +07:00
Anatoliy Chakkaev
1c8194a7ce
Merge pull request #2 from sdrdis/master
...
Added support for include key
2012-12-16 16:39:19 -08:00
Sébastien Drouyer
7a69062f47
added support for include key
2012-12-16 18:57:39 +01:00
Sascha Gehlich
d433ba7efe
add additional Point type to the schema
2012-12-16 14:27:30 +01:00
Anatoliy Chakkaev
2eed9a6e89
Init
2012-12-14 18:01:44 +04:00