I have the regular default database where people post jobs and would like to add an extra database for people to submit registration type information like address, phone, etc. that is not to be viewed by the public and also another dbman database where people can post resumes and can be viewed by the public. All will require unique fields. 3 dbmans and not sure where to start. The main default db is almost complete and haven't started the other 2.. Is there a tutorial anywhere on here or a great thread that will point me in the right direction? I don't know the difficulty involved> I am a beginner in Perl... Where should I turn?
Jul 13, 1999, 2:04 PM
Novice (9 posts)
Jul 13, 1999, 2:04 PM
Post #2 of 17
Views: 5333
Hi wave3,
I'm a hack at this too, just picking up Perl as I use scripts like this one. But I have somehow gotten about 5 or 6 databases all running off of the core dbman engine. Here's how:
Once I have one set up the way I like it, then I copy the files I need to be unique and specify them as a whole new set:
- blah.cfg
- blah.db
- blah.pass
- blah.count
- blah.log
- blah_html.pl
But I can keep just one copy of db.cgi. From there, you just need to modify blah.cfg to point to all the right components and then start modifying it all! And if you share the same password info, you can share that file too. Or the log, if you like.
In one case I have two configurations viewing the same db data -- one brief set of views for the public, and one detailed set for my editors. Same passwd, same log, same count. Different .cfg and html.pl files though.
Once you have more than one set up, just remember to point your URLs appropriately:
http://www.xxx.edu/dbman/db.cgi <-- default db
http://www.xxx.edu/dbman/db.cgi?db=blah <-- blah db
http://www.xxx.edu/dbman/db.cgi?db=foo <-- foo db
Hope this helps,
Neal
[This message has been edited by nmagee (edited July 13, 1999).]
I'm a hack at this too, just picking up Perl as I use scripts like this one. But I have somehow gotten about 5 or 6 databases all running off of the core dbman engine. Here's how:
Once I have one set up the way I like it, then I copy the files I need to be unique and specify them as a whole new set:
- blah.cfg
- blah.db
- blah.pass
- blah.count
- blah.log
- blah_html.pl
But I can keep just one copy of db.cgi. From there, you just need to modify blah.cfg to point to all the right components and then start modifying it all! And if you share the same password info, you can share that file too. Or the log, if you like.
In one case I have two configurations viewing the same db data -- one brief set of views for the public, and one detailed set for my editors. Same passwd, same log, same count. Different .cfg and html.pl files though.
Once you have more than one set up, just remember to point your URLs appropriately:
http://www.xxx.edu/dbman/db.cgi <-- default db
http://www.xxx.edu/dbman/db.cgi?db=blah <-- blah db
http://www.xxx.edu/dbman/db.cgi?db=foo <-- foo db
Hope this helps,
Neal
[This message has been edited by nmagee (edited July 13, 1999).]
Jul 13, 1999, 2:35 PM
Novice (45 posts)
Jul 13, 1999, 2:35 PM
Post #3 of 17
Views: 5356
thankyou nmagee! It seems to make sense. I'll just start copying files and doing some renaming. I'll make sure to point the files to the right location... I'm sure I may run in to some surprises but I'm extremely impressed with the support on here and how smoothly the first one went.
Thanks for taking the time to reply... If you're out there jpdeni and know some things I should look at for I'm all ears...
Thanks for taking the time to reply... If you're out there jpdeni and know some things I should look at for I'm all ears...
Jul 26, 1999, 11:52 PM
Novice (16 posts)
Jul 26, 1999, 11:52 PM
Post #10 of 17
Views: 5324
hmm... still having problems... putting http://..../db.cgi?music does not get me into the music db, but http://..../db.cgi?db=music appears to, but then any commands (click on view, etc) cause browser to hang... (the links all point to the default database anyhow - somehow, it does not pick up the database from the URL...)
[This message has been edited by ludwig (edited July 27, 1999).]
[This message has been edited by ludwig (edited July 27, 1999).]
Jul 27, 1999, 3:50 AM
Novice (45 posts)
Jul 27, 1999, 3:50 AM
Post #12 of 17
Views: 5358
Ludwig, I was having the same problem at first. I'm new at this but I'll tell you why I had that problem. Early on I changed only one small thing in db.cgi. and it caused exactly what you are talking about. I put a uid in the db.cgi and it caused the problem. So I changed it back to what it originally said which was
# Load the form information and set the config file and userid.
local(%in) = &parse_form;
$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'default');
$in{'uid'} ? ($db_uid = $in{'uid'}): ($db_uid = ''
and all was ok. I don't know if this is what happened but JPDeni is a master of this script and will find your troubles if you never touched this,,,
Good luck
# Load the form information and set the config file and userid.
local(%in) = &parse_form;
$in{'db'} ? ($db_setup = $in{'db'}) : ($db_setup = 'default');
$in{'uid'} ? ($db_uid = $in{'uid'}): ($db_uid = ''
and all was ok. I don't know if this is what happened but JPDeni is a master of this script and will find your troubles if you never touched this,,,
Good luck
Jul 27, 1999, 4:00 AM
Novice (16 posts)
Jul 27, 1999, 4:00 AM
Post #13 of 17
Views: 5334
no, I did not alter that at all... in fact, the only thing I changed in db.cgi was the path to perl!!
I tried putting in the absolute path to the scripts, but that just confused it and gave errors... so I put it back the way it was..
i have installed loads of scripts, so I'm not a complete greenhorn, but this one has me stumped. (
I tried putting in the absolute path to the scripts, but that just confused it and gave errors... so I put it back the way it was..
i have installed loads of scripts, so I'm not a complete greenhorn, but this one has me stumped. (
Jul 28, 1999, 6:34 AM
Veteran / Moderator (8669 posts)
Jul 28, 1999, 6:34 AM
Post #16 of 17
Views: 5349