mysql: not null / required column #110

Activity

1. dresende commented on Apr 10, 2013

   

   dresende

   on Apr 10, 2013

   Owner

   More actions

   There isn't yet, I'll work on it.
2. dresende

   added a commit that references this issue on Apr 10, 2013

   Adds default settings properties.not_null = false (#110)

   84645c8
3. dresende commented on Apr 10, 2013

   

   dresende

   on Apr 10, 2013

   Owner

   More actions

   Get the latest git version and try this (adjust to your code):

   orm.settings.set("properties.not_null", true); // changes default to NOT NULL
   
   orm.connect("mysql://....", function (err, db) {
       var Person = db.define('person', {
           name : String
       });
       Person.sync();
   
       // ...
   });
4. GoNode5 commented on Apr 10, 2013

   

   GoNode5

   on Apr 10, 2013

   Author

   More actions

   ok your very fast. Thanks for all your help.... The next problem is existing tables... how to add null? And what about validation... it would be great if this was also default handled (you cant create an item anyway...)
5. dresende commented on Apr 10, 2013

   

   dresende

   on Apr 10, 2013

   Owner

   More actions

   Existing tables are more hard to handle but it's in the plans (#103). For validations look at the first example in the Readme. I know the documentation is scarse but I tend to code more and document less.
6. dxg commented on Apr 10, 2013

   

   dxg

   on Apr 10, 2013

   Collaborator

   More actions

   Probably just nitpicking, but could we call this setting 'required' just like we have on has one associations? It does the same thing. I'm also thinking that 'notnull' may not make sense for non-sql datastores. 'required' is more general.
7. dresende commented on Apr 11, 2013

   

   dresende

   on Apr 11, 2013

   Owner

   More actions

   Agree
8. dresende

   closed this as completedon Apr 11, 2013