[Koha-cvs] CVS: koha/marc marcschema.sql,1.6,1.7 perlmarcstructure,1.1,1.2

[Steve Tonnesen]

Update of /cvsroot/koha/koha/marc
In directory usw-pr-cvs1:/tmp/cvs-serv13168

Modified Files:
        marcschema.sql perlmarcstructure 
Log Message:
Changed subfieldmark back to subfieldcode


Index: marcschema.sql
===================================================================
RCS file: /cvsroot/koha/koha/marc/marcschema.sql,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** marcschema.sql      29 May 2002 21:11:41 -0000      1.6
--- marcschema.sql      29 May 2002 22:11:20 -0000      1.7
***************
*** 19,27 ****
                bibid bigint(20) NOT NULL default '0',
                subfieldorder tinyint(4) NOT NULL default '0',
!               subfieldmark char(1) NOT NULL default '',
                subfieldvalue varchar(255) default NULL,
                valuebloblink bigint(20) default NULL,
                PRIMARY KEY (subfieldid),
!               KEY (bibid,tagid,tag,subfieldmark),
                ) TYPE=MyISAM;
  
--- 19,27 ----
                bibid bigint(20) NOT NULL default '0',
                subfieldorder tinyint(4) NOT NULL default '0',
!               subfieldcode char(1) NOT NULL default '',
                subfieldvalue varchar(255) default NULL,
                valuebloblink bigint(20) default NULL,
                PRIMARY KEY (subfieldid),
!               KEY (bibid,tagid,tag,subfieldcode),
                ) TYPE=MyISAM;
  

Index: perlmarcstructure
===================================================================
RCS file: /cvsroot/koha/koha/marc/perlmarcstructure,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -r1.1 -r1.2
*** perlmarcstructure   22 May 2002 16:00:51 -0000      1.1
--- perlmarcstructure   29 May 2002 22:11:20 -0000      1.2
***************
*** 38,41 ****
--- 38,46 ----
                                             are 110 tags
  
+ Need a similar index for subfields.... I'm not sure if this is any simpler 
than
+ just looping through the tags every time.  :)
+ 
+ I think looping is the way to go...
+ 
  This still needs more work.  This will also require an API for accessing or
  modifying this structure, as it is non-trivial to parse the data.  I'm also