line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
|
2
|
|
|
|
|
|
|
use warnings; |
3
|
1
|
|
|
1
|
|
124937
|
use strict; |
|
1
|
|
|
|
|
2
|
|
|
1
|
|
|
|
|
35
|
|
4
|
1
|
|
|
1
|
|
4
|
|
|
1
|
|
|
|
|
2
|
|
|
1
|
|
|
|
|
42
|
|
5
|
|
|
|
|
|
|
=head1 NAME |
6
|
|
|
|
|
|
|
|
7
|
|
|
|
|
|
|
OpenERP::OOM - OpenERP Object to Object Mapper |
8
|
|
|
|
|
|
|
|
9
|
|
|
|
|
|
|
=cut |
10
|
|
|
|
|
|
|
|
11
|
|
|
|
|
|
|
our $VERSION = '0.48'; |
12
|
|
|
|
|
|
|
|
13
|
|
|
|
|
|
|
=head1 SYNOPSIS |
14
|
|
|
|
|
|
|
|
15
|
|
|
|
|
|
|
OpenERP::OOM (Object to Object Mapper) maps OpenERP objects to Perl objects, in |
16
|
|
|
|
|
|
|
a similar way to how an ORM like DBIx::Class maps database tables to Perl classes. |
17
|
|
|
|
|
|
|
|
18
|
|
|
|
|
|
|
Relationships between objects can be defined in Perl code so that the OpenERP |
19
|
|
|
|
|
|
|
schema can be traversed using Perl method calls, and related objects can be created |
20
|
|
|
|
|
|
|
by calling methods on their parent (again, this corresponds closely to the |
21
|
|
|
|
|
|
|
relationship model in an ORM). |
22
|
|
|
|
|
|
|
|
23
|
|
|
|
|
|
|
Additionally, links can be defined to join OpenERP objects with DBIx::Class |
24
|
|
|
|
|
|
|
schemas, so that an OpenERP object can be augmented with additional data |
25
|
|
|
|
|
|
|
structures, methods, and application logic that is held outside of OpenERP. |
26
|
|
|
|
|
|
|
|
27
|
|
|
|
|
|
|
=head1 TUTORIAL |
28
|
|
|
|
|
|
|
|
29
|
|
|
|
|
|
|
L<OpenERP::OOM::Tutorial> gives a walkthrough of how to use OpenERP::OOM. |
30
|
|
|
|
|
|
|
|
31
|
|
|
|
|
|
|
|
32
|
|
|
|
|
|
|
=cut |
33
|
|
|
|
|
|
|
|
34
|
|
|
|
|
|
|
1; # End of OpenERP::OOM |