Projekt

Allgemein

Profil

« Zurück | Weiter » 

Revision fa7c3cb5

Von Bernd Bleßmann vor fast 11 Jahren hinzugefügt

  • ID fa7c3cb5774b65d53cd5f4cdbb9443ad7e8ac671
  • Vorgänger c6043e02
  • Nachfolger 1cc72c5b

Verwendung von datatype in der Doku deutlicher herausgestellt.

Unterschiede anzeigen:

SL/Helper/Csv.pm
446 446
If not given, headers are taken from the first n lines of data, where n is the
447 447
number of different class types.
448 448

  
449
In case of multiplexed data the first column must be named 'datatype'. This
450
name must be given in the header.
451

  
449 452
Examples:
450 453

  
451 454
  classic data of one type:
452 455
  [ 'name', 'street', 'zipcode', 'city' ]
453 456

  
454 457
  multiplexed data with two different types
455
  [ [ 'ordernumber', 'customer', 'transdate' ], [ 'partnumber', 'qty', 'sellprice' ] ]
458
  [ [ 'datatype', 'ordernumber', 'customer', 'transdate' ],
459
    [ 'datatype', 'partnumber', 'qty', 'sellprice' ] ]
456 460

  
457 461
=item C<profile> [{profile => \%ACCESSORS, class => class, row_ident => ri},]
458 462

  
......
493 497
and the return value used instead of the line itself.
494 498

  
495 499
C<row_ident> is a string to recognize the right profile and class for each data
496
line in multiplexed data.
500
line in multiplexed data. It must match the value in the column 'dataype' for
501
each class.
497 502

  
498 503
In case of multiplexed data, C<class> and C<row_ident> must be given.
499 504
Example:

Auch abrufbar als: Unified diff