Add One2One field

[bch, 2010-09-05 22:18:40]

http://codereview.appspot.com/2126043/diff/1/8
File trytond/test/test.py (right):

http://codereview.appspot.com/2126043/diff/1/8#newcode389
trytond/test/test.py:389: 'Origin and target must be unique'),
If i understand correctly, to have a one2one, we have to define two constraint:
unique('target') and unique('origin').

[udono, 2010-10-11 22:09:06]

http://codereview.appspot.com/2126043/diff/7001/doc/ref/models/fields.rst
File doc/ref/models/fields.rst (right):

http://codereview.appspot.com/2126043/diff/7001/doc/ref/models/fields.rst#new...
doc/ref/models/fields.rst:518: .. method:: Many2Many.get_target(pool)
One2One.get_target(pool) ?

[pheller, 2010-11-17 00:49:59]

http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py
File trytond/test/test.py (right):

http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py#newcode412
trytond/test/test.py:412: origin = fields.Many2One('test.one2one_required',
'Origin')
Ok, just now getting around to giving this a try.  At first glance, I'm a bit
confused.  Given my example (ethernet interfaces can have one other end), I'd
like to define a model like so:


class Interface(ModelSQL, ModelView):
    'Interface'
    _name = 'imdb.interface'
    _description = __doc__
    name = fields.Char('Name')
    device = fields.Many2One('imdb.device', 'Device')
    other = fields.One2One('imdb.interface.relation', 'other', 'Other
Interface')
Interface()

So, I guess I have these questions:

Must I define the "relation" model?
Is it possible for the relation model's origin and targets refer to the same
model?

[pheller, 2010-11-17 00:52:08]

Don't think this sent, resending.

On 2010/11/17 00:49:59, pheller wrote:
> http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py
> File trytond/test/test.py (right):
> 
>
http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py#newcode412
> trytond/test/test.py:412: origin = fields.Many2One('test.one2one_required',
> 'Origin')
> Ok, just now getting around to giving this a try.  At first glance, I'm a bit
> confused.  Given my example (ethernet interfaces can have one other end), I'd
> like to define a model like so:
> 
> 
> class Interface(ModelSQL, ModelView):
>     'Interface'
>     _name = 'imdb.interface'
>     _description = __doc__
>     name = fields.Char('Name')
>     device = fields.Many2One('imdb.device', 'Device')
>     other = fields.One2One('imdb.interface.relation', 'other', 'Other
> Interface')
> Interface()
> 
> So, I guess I have these questions:
> 
> Must I define the "relation" model?
> Is it possible for the relation model's origin and targets refer to the same
> model?

[ced, 2010-11-17 08:38:07]

http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py
File trytond/test/test.py (right):

http://codereview.appspot.com/2126043/diff/36001/trytond/test/test.py#newcode412
trytond/test/test.py:412: origin = fields.Many2One('test.one2one_required',
'Origin')
On 2010/11/17 00:50:00, pheller wrote:
> Ok, just now getting around to giving this a try.  At first glance, I'm a bit
> confused.  Given my example (ethernet interfaces can have one other end), I'd
> like to define a model like so:
> 
> 
> class Interface(ModelSQL, ModelView):
>     'Interface'
>     _name = 'imdb.interface'
>     _description = __doc__
>     name = fields.Char('Name')
>     device = fields.Many2One('imdb.device', 'Device')
>     other = fields.One2One('imdb.interface.relation', 'other', 'Other
> Interface')
> Interface()
> 
> So, I guess I have these questions:
> 
> Must I define the "relation" model?

Yes

> Is it possible for the relation model's origin and targets refer to the same
> model?   

Yes