如何使用mysql实现关系数据库(How to implement relational database using mysql)

 好的，首先解决方法是在attr上使用update功能。 看看这个旋风 。 
 
 我用this.set('name', 'tom')和this.attrs.name.update('tom')带有{{attrs.name}} {{name}}替换了this.set('name', 'tom') 。 
 
 解决方法的另一种方法就是在Ember.run.later中包装asignment，就像我在这里完成的那样，我用this.set('name', 'tom')替换了this.set('name', 'tom') ： 
 
Ember.run.later(() => {
  this.set('name', 'tom');
});
 
 
 这就是解决方法。 
 
 绑定未在init上完全设置的事实有很长的历史。 但通常它是一个反模式来初始化子组件中的值并将该值提供给父组件。 它使您的代码可读性降低，并且再次成为DDAU （Data down，Actions up）原则。 
 
 我建议在创建模型时显式初始化数据，而不是在组件评估周期中隐式显示。 
 
 对于您不想存储的默认值，我建议您编写计算属性： 
 
nameWithDefault: computed('name', {
    get() {
        return get(this, 'name') || 'tom';
    },
    set(key, val) {
        set(this, 'name', val);
    }
})
 
 这是显式的，不会在查看组件后写下数据，并且适用于用户。 

Okay, first a way to work around is to use the update function on the attr. Checkout this twiddle.
 
I replaced this.set('name', 'tom') with this.attrs.name.update('tom') in the .js and {{name}} with {{attrs.name}} in the .hbs.
 
Another way to work around is just to wrap the asignment in a Ember.run.later like I've done here, where I replaced this.set('name', 'tom') with that:
 
Ember.run.later(() => {
  this.set('name', 'tom');
});
 
 
So that are the workarounds.
 
The fact that the bindings are not completely set up on init has a long history. But generally its an anti pattern to initialize a value in a child component and give this value up to the parent. It makes your code less readable and is agains the DDAU (Data down, Actions up) principle.
 
I recommend to initialize the data explicit when you create your models, not implicit during your component evaluation cycle.
 
For default values that you don't want to store I recommend you to write a computed property:
 
nameWithDefault: computed('name', {
    get() {
        return get(this, 'name') || 'tom';
    },
    set(key, val) {
        set(this, 'name', val);
    }
})
 
This is explicit, does not write down the data after a component is viewed, and works for the user.