massive-js issueshttps://gitlab.com/dmfay/massive-js/-/issues2012-12-01T01:22:47Zhttps://gitlab.com/dmfay/massive-js/-/issues/5support sqlserver 2012-12-01T01:22:47ZDian Faysupport sqlserver *Created by: aozora*
Please consider to support sql server via it's official driver.
*Created by: aozora*
Please consider to support sql server via it's official driver.
https://gitlab.com/dmfay/massive-js/-/issues/3more than one row returned by a subquery used as an expression2012-12-03T18:34:21ZBrad Tellermore than one row returned by a subquery used as an expressionWhen multiple key constraints are defined for a table this error is thrown and the server will not start.
The issue is the query in ./lib/postgres.js in this.tableSQL. That query isn't specifically targeting primary keys.
When multiple key constraints are defined for a table this error is thrown and the server will not start.
The issue is the query in ./lib/postgres.js in this.tableSQL. That query isn't specifically targeting primary keys.
https://gitlab.com/dmfay/massive-js/-/issues/2Update NPM Package2012-12-03T18:34:42ZDian FayUpdate NPM Package*Created by: Kwal*
Pretty please? =)
*Created by: Kwal*
Pretty please? =)
https://gitlab.com/dmfay/massive-js/-/issues/9Suggestion: use node-any-db2013-03-30T19:44:26ZChakritSuggestion: use node-any-dbReference: https://github.com/grncdr/node-any-db
So we don't have to install both mysql and pg module and the connection, transaction and sql execution interface is normalized between pg and mysql.
Reference: https://github.com/grncdr/node-any-db
So we don't have to install both mysql and pg module and the connection, transaction and sql execution interface is normalized between pg and mysql.
https://gitlab.com/dmfay/massive-js/-/issues/14Joins and Transactions, they are implemented?2014-04-29T20:46:49ZOsvaldoTCFJoins and Transactions, they are implemented?Joins and Transactions, they are implemented?
How can I use them?
Joins and Transactions, they are implemented?
How can I use them?
https://gitlab.com/dmfay/massive-js/-/issues/13Does massive support upsert?2014-04-29T20:47:13ZDian FayDoes massive support upsert?*Created by: andosaur*
Thanks for the great library.
As per title, does massive support upsert?
*Created by: andosaur*
Thanks for the great library.
As per title, does massive support upsert?
https://gitlab.com/dmfay/massive-js/-/issues/16Calling first on dataset ignores select columns2014-05-24T13:20:26ZMacarioCalling first on dataset ignores select columns db.users.first({email: userEmail},{columns: ['email', 'secret']}).execute(function(res){
// res contains includes all columns
})
db.users.first({email: userEmail},{columns: ['email', 'secret']}).execute(function(res){
// res contains includes all columns
})
https://gitlab.com/dmfay/massive-js/-/issues/20mysql package is old2015-03-04T19:27:06ZDian Faymysql package is old*Created by: magicbrighter*
mysql package version is 0.95 ,but mainline of mysql is 2.1.x. 2.1.x fix more bugs like auto reconnect etc. Do you have plan update mysql package
*Created by: magicbrighter*
mysql package version is 0.95 ,but mainline of mysql is 2.1.x. 2.1.x fix more bugs like auto reconnect etc. Do you have plan update mysql package
https://gitlab.com/dmfay/massive-js/-/issues/19Link on npmjs.com is wrong?2015-03-04T19:31:00ZMatthijs KooijmanLink on npmjs.com is wrong?https://www.npmjs.com/package/massive links to the C# version at https://github.com/robconery/massive
https://www.npmjs.com/package/massive links to the C# version at https://github.com/robconery/massive
https://gitlab.com/dmfay/massive-js/-/issues/18find with arguments returns empty array.2015-03-04T19:34:54ZDian Fayfind with arguments returns empty array.*Created by: ymitis*
Is anyone else not getting results when issuing a find command with arguments? I'm trying to connect to MySql. The following code returns an empty array:
db.Users.find({id: 1}).execute(function(err, users) {
...*Created by: ymitis*
Is anyone else not getting results when issuing a find command with arguments? I'm trying to connect to MySql. The following code returns an empty array:
db.Users.find({id: 1}).execute(function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
However the following returns the user:
db.run('SELECT \* FROM Users WHERE id = 1',function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
Also note the following returns the entire collection of users:
db.Users.find().execute(function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
The execute function in mysql.js ....
client.query(sql, params, function(err, results){
The sql variable value = SELECT \* FROM Users WHERE "id" = 1
Notice that field name id is in quotations, I don't think it should.
Is there something I'm doing wrong? or is it a bug? I haven't been able to identity the bug yet but I will keep looking.
https://gitlab.com/dmfay/massive-js/-/issues/21Namespace file queries based on directory2015-03-05T17:25:39ZRob ConeryNamespace file queries based on directoryRight now we read in the files and drop them right on the root namespace. Would be better to have namespacing by directory. We currently have `glob` installed but not sure how to handle this best.
Right now we read in the files and drop them right on the root namespace. Would be better to have namespacing by directory. We currently have `glob` installed but not sure how to handle this best.
https://gitlab.com/dmfay/massive-js/-/issues/24Add support for SQL Server2015-03-05T20:47:04ZRob ConeryAdd support for SQL ServerJust kidding
Just kidding
https://gitlab.com/dmfay/massive-js/-/issues/23Clean up index.js to inherit or namespace other modules2015-03-06T20:57:53ZRob ConeryClean up index.js to inherit or namespace other modulesRight now it's a bit of a dump ground, needs some cleaning
Right now it's a bit of a dump ground, needs some cleaning
https://gitlab.com/dmfay/massive-js/-/issues/22Add count, first, last etc for table queries to bring parity to Massive v12015-03-06T20:58:27ZRob ConeryAdd count, first, last etc for table queries to bring parity to Massive v1https://gitlab.com/dmfay/massive-js/-/issues/29Refactor File Walker/Script Assignment2015-03-08T07:47:17ZDian FayRefactor File Walker/Script Assignment*Created by: xivSolutions*
Pull out the function assignment from the file walking bits.
@robconery Earlier on, you had thought you wanted to fie walk/Function assignment pulled out of index.js. You have since moved it back. Did you wa...*Created by: xivSolutions*
Pull out the function assignment from the file walking bits.
@robconery Earlier on, you had thought you wanted to fie walk/Function assignment pulled out of index.js. You have since moved it back. Did you want to keep it there now, or did you still want to pull it out?
It's two functions now - easier to read/understand, but potentially dirtying up index.js with noise.
What say you?
https://gitlab.com/dmfay/massive-js/-/issues/30Account for schemas in loadTables2015-03-09T14:06:54ZRob ConeryAccount for schemas in loadTablesRight now we're just dropping things from `public` right on to the massive instance which works for many situations. I think it would be better to account for schemas as well - as that's [a good approach for keeping your DB uncluttered](...Right now we're just dropping things from `public` right on to the massive instance which works for many situations. I think it would be better to account for schemas as well - as that's [a good approach for keeping your DB uncluttered](http://www.postgresql.org/docs/9.4/static/ddl-schemas.html) when it gets to be rather large.
> There are several reasons why one might want to use schemas:
> - To allow many users to use one database without interfering with each other.
> - To organize database objects into logical groups to make them more manageable.
> - Third-party applications can be put into separate schemas so they do not collide with the names of other objects.
>
> Schemas are analogous to directories at the operating system level, except that schemas cannot be nested.
Our current tableSql pulls the schema (I think) so we have access to it. If the schema is `public` I say we do what we've been doing (pop it onto the massive instance). If it's not, namespace thus:
``` javacript
db.my_schema.my_table.find()
```
https://gitlab.com/dmfay/massive-js/-/issues/33Add Tests for Add/Update/Delete2015-03-10T04:53:28ZDian FayAdd Tests for Add/Update/Delete*Created by: xivSolutions*
*Created by: xivSolutions*
https://gitlab.com/dmfay/massive-js/-/issues/36Add tests for document add/update/delete2015-03-13T05:57:15ZDian FayAdd tests for document add/update/delete*Created by: xivSolutions*
*Created by: xivSolutions*
https://gitlab.com/dmfay/massive-js/-/issues/38Support Oracle2015-03-14T08:45:15ZDian FaySupport Oracle*Created by: jbogard*
I noticed that this project does not support Oracle.
Please support Oracle.
Also, is this project still being actively developed? The last commit was over 4 hours ago.
*Created by: jbogard*
I noticed that this project does not support Oracle.
Please support Oracle.
Also, is this project still being actively developed? The last commit was over 4 hours ago.
https://gitlab.com/dmfay/massive-js/-/issues/34Add Test for Document Insert/Update/Deletes2015-03-14T14:18:51ZDian FayAdd Test for Document Insert/Update/Deletes*Created by: xivSolutions*
*Created by: xivSolutions*