Yesterday I asked for the structure of the websites table. I still have no answers. Today, I will ask for the "uploadedmarc" table structure (in acqui.simple). PLEASE, when you update you local mysql-DB, don't forget cvs ignore it, so update database.mysql immediatly, so I will be able to do the changes also... I've searched "uploadedmarc" table everywhere and could'nt find it ;-((( Thanks. This day was a boring day : searching for biblio-adding problem without any result, and trying to work on marc stuff with no more success :-\\\\\\\ -- Paul
paul POULAIN wrote:
paul POULAIN wrote:
Yesterday I asked for the structure of the websites table. I still have no answers.
Today, I will ask for the "uploadedmarc" table structure (in acqui.simple).
Same question for : z3950queue uploadedmarc marcrecorddone z3950results
Oops, the z3950 tables are defined in updatedatabase script. OK for those. But the question is still here for the "marc" tables. -- Paul
On Wed, 15 May 2002, paul POULAIN wrote:
uploadedmarc marcrecorddone
mysql> show columns from marcrecorddone; +---------------+----------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+----------+------+-----+---------+-------+ | isbn | char(40) | YES | | NULL | | | issn | char(40) | YES | | NULL | | | lccn | char(40) | YES | | NULL | | | controlnumber | char(40) | YES | | NULL | | +---------------+----------+------+-----+---------+-------+ mysql> show columns from uploadedmarc; +--------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +--------+--------------+------+-----+---------+----------------+ | id | int(11) | | PRI | NULL | auto_increment | | marc | longblob | YES | | NULL | | | hidden | smallint(6) | YES | | NULL | | | name | varchar(255) | YES | | NULL | | +--------+--------------+------+-----+---------+----------------+ Paul: Do you want to meet on IRC to discuss MARC for a bit? Steve.
On Thu, 2002-05-16 at 03:27, paul POULAIN wrote:
Yesterday I asked for the structure of the websites table. I still have no answers.
The websites table is in the database.mysql file in cvs Paul. Its in the main branch, not the rel-1-2 branch, since this new code gynn has been working on is not destined for 1.2. Revision 1.7 is where the update occured. If you take a look at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/koha/koha/database.mysql You'll see it there. I think you have been looking at the rel-1-2 branch database.mysql file ... Which in theory shouldnt have any of the new stuff like marc, websites etc in it yet.
Today, I will ask for the "uploadedmarc" table structure (in acqui.simple).
PLEASE, when you update you local mysql-DB, don't forget cvs ignore it, so update database.mysql immediatly, so I will be able to do the changes also... I've searched "uploadedmarc" table everywhere and could'nt find it ;-(((
Im not sure about these other tables, but we do need to make sure we are working on the correct branch. So that we dont miss things. Or commit changes to places we dont want them. Chris -- Chris Cormack chris@katipo.co.nz Programmer 025 500 579 Katipo Communications www.katipo.co.nz
It seems i've problems with cvs... so, what I do : * if i want to work on rel_1_2 branch : # cvs -z3 -b rel_1_2 -d:ext:tipaul@cvs.koha.sourceforge.net:/cvsroot/koha co koha It update my local files to "rel_1_2" status. Then I work. Then I do # cvs commit file_modified It commits file_modified to the rel_1_2 branch. * if i want to work on main branch (development one), i do : # cvs -z3 -d:ext:tipaul@cvs.koha.sourceforge.net:/cvsroot/koha co koha It updates my local files to main branch. Then I work. Then I do # cvs commit file_modified It commits file_modified to main branch. I just tried to do it on main branch, and it does nothing... So I think i'm doing something wrong, but what ? Hi Paul What I have, is 3 checkouts running at the moment. What i did was checkout the main branch and its now called koha-main. Checked out the rel-1-2 branch and moved it to koha-rel-1-2 and checked out the rel-1-4-marc one. This is probably a bit of a workaround on my part. But it seems to work well, in terms of working in separate branches. Id be interested in hearing how others work. Question for bugfixes : if i du a small bugfix that affect 1_2 branch as well as main one, how do i commit the change in both ? or maybe i just have to correct in 1_2 branch and we have a method to copy it to the main one after. Im fairly certain we can merge changes back from a branch into the main. http://www.cvshome.org/docs/manual/cvs_5.html#SEC61 Tells you a little bit about it. Im not sure whether there is a french version of these documents. Question 2 : how to avoid having to type my "# tipaul@cvs.koha.sourceforge.net's password:" 50 times a day ? Ahh this question i can actually answer with some certainty. You can generate keys for use with ssh, if you do this it will use the keys to connect instead. And you wont have to type your password. https://sourceforge.net/docman/display_doc.php?docid=761&group_id=1 Tells you about it. Chris -- Chris Cormack chris@katipo.co.nz Programmer 025 500 579 Katipo Communications www.katipo.co.nz
On 16 May 2002, Chris Cormack wrote:
(I think this bit is from Paul)
It seems i've problems with cvs... so, what I do : * if i want to work on rel_1_2 branch : # cvs -z3 -b rel_1_2 -d:ext:tipaul@cvs.koha.sourceforge.net:/cvsroot/koha co koha It update my local files to "rel_1_2" status. Then I work. Then I do # cvs commit file_modified It commits file_modified to the rel_1_2 branch.
* if i want to work on main branch (development one), i do : # cvs -z3 -d:ext:tipaul@cvs.koha.sourceforge.net:/cvsroot/koha co koha It updates my local files to main branch. Then I work. Then I do # cvs commit file_modified It commits file_modified to main branch.
I just tried to do it on main branch, and it does nothing... So I think i'm doing something wrong, but what ?
Hi Paul
What I have, is 3 checkouts running at the moment. What i did was checkout the main branch and its now called koha-main. Checked out the rel-1-2 branch and moved it to koha-rel-1-2 and checked out the rel-1-4-marc one.
This is probably a bit of a workaround on my part. But it seems to work well, in terms of working in separate branches.
This is what I do as well. I have a koha directory with koha, rc, and rel_1_2 subdirs. koha contains a checkout from the main line, rc has an unpacked copy of the latest RC tarball, and rel_1_2 contains a checkout from the rel_1_2 branch. For the moment I'm ignoring the rel-1-4 branch, but will eventually create a dir for that as well (when we're ready to start merging 1.2 fixes into 1.3).
Id be interested in hearing how others work.
Question for bugfixes : if i du a small bugfix that affect 1_2 branch as well as main one, how do i commit the change in both ? or maybe i just have to correct in 1_2 branch and we have a method to copy it to the main one after.
Im fairly certain we can merge changes back from a branch into the main. http://www.cvshome.org/docs/manual/cvs_5.html#SEC61 Tells you a little bit about it. Im not sure whether there is a french version of these documents.
Yes, this can be done. Another source to read through is: http://cvsbook.red-bean.com/cvsbook.html#Merging_Changes_From_Branch_To_Trun... (which also has spanish, german, and japanese translations. french isn't there yet, but it is under an open license so there is nothing blocking someone from starting a translation.)
Question 2 : how to avoid having to type my "# tipaul@cvs.koha.sourceforge.net's password:" 50 times a day ?
Ahh this question i can actually answer with some certainty. You can generate keys for use with ssh, if you do this it will use the keys to connect instead. And you wont have to type your password.
https://sourceforge.net/docman/display_doc.php?docid=761&group_id=1
Tells you about it.
Chris
participants (4)
-
Chris Cormack -
Pat Eyler -
paul POULAIN -
Tonnesen Steve