32 |
one value) it's not a great loss. However, you will have to re-write |
one value) it's not a great loss. However, you will have to re-write |
33 |
your C<import_xml> files if you use lookup files to use memory lookups. |
your C<import_xml> files if you use lookup files to use memory lookups. |
34 |
|
|
35 |
|
Lookups B<are not> specified by C<[v900^4]> as in v1.x. Now, you have |
36 |
|
to use something like C<lookup{v900^4}>. Recursive lookups are also |
37 |
|
possible: C<lookup{foo:lookup{v900^4}}>. |
38 |
|
|
39 |
Memory lookups (referred as lookups for new versions of WebPAC) are now |
Memory lookups (referred as lookups for new versions of WebPAC) are now |
40 |
available always. Since whole database is available when creating |
always available. Since whole database is available when creating |
41 |
output linking should be much easier now. |
output linking should be much easier now. |
42 |
|
|
43 |
However, using new lookups require to define lookups in different way. |
However, using new lookups require to define lookups in different way. |
44 |
Additional benefit of that is conditional insert into lookup using eval. |
Additional benefit of that is conditional insert into lookup using eval |
45 |
|
(TODO: explain new lookup format). |
46 |
|
|
47 |
|
If you have any lookups in your tag (e.g. <isis>lookup{v900^5}</isis>) |
48 |
|
smart delimiters will be turned off (this behaviour is consistent with |
49 |
|
old in v1.x if you use C<type="lookup*"> or C<filter="mem_lookup">). |
50 |
|
|
51 |
=head2 Field definition in C<import_xml> |
=head2 Field definition in C<import_xml> |
52 |
|
|