Permalink
Browse files

This is crashing when using the memory adapter, not sure if it's need…

…ed or not, it doesn't seem affect mono if we don't have it and might not need to be the default
  • Loading branch information...
1 parent 97742e7 commit 8b46f9c454b5db6bf1087f27b10541ea79702692 @MiguelMadero committed Oct 1, 2012
Showing with 0 additions and 10 deletions.
  1. +0 −5 templates/resource/model.ejs
  2. +0 −5 templates/scaffold/model.ejs
@@ -13,11 +13,6 @@ var <%= names.constructor.singular %> = function () {
<% } -%>
});
-<% for(var i in properties) { -%>
-<% if(properties[i].name === 'id' && properties[i].type === 'int') { -%>
- this.autoIncrementId = true;
-<% } -%>
-<% } -%>
this.adapter = 'memory';
/*
@@ -13,11 +13,6 @@ var <%= names.constructor.singular %> = function () {
<% } -%>
});
-<% for(var i in properties) { -%>
-<% if(properties[i].name === 'id' && properties[i].type === 'int') { -%>
- this.autoIncrementId = true;
-<% } -%>
-<% } -%>
this.adapter = 'memory';
/*

3 comments on commit 8b46f9c

I think we need this one for the SQL adapters, not sure though @mde?

mde replied Oct 6, 2012

Yes, we need to assume people want auto-increment when using SQL. How is it crashing?

Owner

MiguelMadero replied Oct 6, 2012

I can't reproduce it. Not sure what the issue was or if there was something else that fixed it :(
I guess I should've documented this better a lot of this issues came from notes when I was playing around.

That said, while trying to reproduce this I found another issue. The int property is created as an integer which causes a validation error ([[model.validatesInteger]])

Please sign in to comment.