Re: Re: more Youch
You shouldn't have to reinstall Linux, just uninstall the old RPM, or delete the old version which was installed from source, and install the new version if it be from RPM or whatever. There is no way that the manual could cover every installation medium that exists (RPM, tar, DEB, BSD Ports tree, etc, etc), so you would have to find the documentation specific to that installation medium (ie the man page on RPM) as it is going to vary from medium to medium. All I was trying to say is that *MY* personal opinion is that system critical packages should be installed from source because it allows you greater control over what is being done, and where it is being put. I am not one for all the "automagic" installation methods in general, if I was I'd be using Windows. Then, even after installation there may be startup scripts and whatnot that need to be modified. This will be especially true if you are installing from source as it makes no assumptions about the type of system you are installing on. So, in short, my suggestion would be to back up any data that is in the database rather it be by using mysqldump or just copying the data directory, uninstalling the old version of MySQL that is on the machine currently, and reinstalling MySQL from fround zero. Another option would be to purchase a support contract from MySQL directly, it looks like the basic support option covers installing from a binary distribution, but you need to buy and extended support option to get assistance with installing from source. Now, in the intrest of the list, I think this flame war should be nipped in the bud, and I will end it with this email. Sean Conley On Wed, 28 Feb 2001, John Jensen wrote: BUG: Telling me I "shouldn't have done" something, not even mentioned in the manual, does not help me fix the problem. BUG: Having to completely reinstall the operating system (Linux) in order to repair problems with a mysql install. Or does someone actually have any recommendations on this? On 27 Feb 2001, at 11:51, Sean Conley wrote: It sounds like the problem is that you originally installed from RPM and later installed from source, or vice versa. RPMs often use a different file layout than source distributions, this is one reason why I always install software that I consider system critical from source, so that there are no unexpected results. As for the socket problem, look here: http://www.mysql.com/doc/C/o/Command-line_options.html Specifically the --socket option which allows you to specify the path to the socket which mysql uses to communicate with the rest of the world. This option is also documented in the New Riders (Paul DuBois) MySQL book, which I have found very useful. Sean On Tue, 27 Feb 2001, John Jensen wrote: There must be a bug here somewhere. I have just made three attempts to reinstall mysql, one from rpm, two from tarball. This is a Redhat6.1 system with 160meg of ram and mysql once ran on it, until I gave it an incorrect shutdown command. (It should not break so easily.) User and group "mysql" already exist, so I just chown chgrp the contents after compiling. This time, I finally got it running, only after copying the old mysql/bin db files to mysql/var. (scripts/mysql_install_db failed to do so, possibly because "scripts" is no longer in the same directory level. Perhaps I untarred the wrong place, but the directions did not seem to tell me where I should.) Once running, mysql absolutely refuses to let me set the root password. It tries to connect through a mysql.sock file in /var/lib/mysql. HELLO Did mysql fail to detect the system installed on? My Redhat7 server uses /var/lib/mysql for all the mysql files. 6.x and earlier versions have the files in /usr/local/mysql. Why is mysql even looking in /var/lib?? I remembered mention of similar problems on the list, so I did a search on the website, but I am turning up messages three years old, with commands like "UPDATE" that are not being recognized. Is there a way to fix this? Do I have to scratch again and start over in the /var/lib directory? I emailed the error files from my last attempt, but it disappeared. This time, the error file just filled with help messages. Do I have to reinstall Redhat with v.7 to make the current mysql release work? Do I have to scratch and use the previous version to make it work on v.6.1? Please help. I'm stumped and frustrated. John Jensen 520 Goshawk Court Bakersfield, CA 93309 661-833-2858 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To u
Re: more Youch
It sounds like the problem is that you originally installed from RPM and later installed from source, or vice versa. RPMs often use a different file layout than source distributions, this is one reason why I always install software that I consider system critical from source, so that there are no unexpected results. As for the socket problem, look here: http://www.mysql.com/doc/C/o/Command-line_options.html Specifically the --socket option which allows you to specify the path to the socket which mysql uses to communicate with the rest of the world. This option is also documented in the New Riders (Paul DuBois) MySQL book, which I have found very useful. Sean On Tue, 27 Feb 2001, John Jensen wrote: There must be a bug here somewhere. I have just made three attempts to reinstall mysql, one from rpm, two from tarball. This is a Redhat6.1 system with 160meg of ram and mysql once ran on it, until I gave it an incorrect shutdown command. (It should not break so easily.) User and group "mysql" already exist, so I just chown chgrp the contents after compiling. This time, I finally got it running, only after copying the old mysql/bin db files to mysql/var. (scripts/mysql_install_db failed to do so, possibly because "scripts" is no longer in the same directory level. Perhaps I untarred the wrong place, but the directions did not seem to tell me where I should.) Once running, mysql absolutely refuses to let me set the root password. It tries to connect through a mysql.sock file in /var/lib/mysql. HELLO Did mysql fail to detect the system installed on? My Redhat7 server uses /var/lib/mysql for all the mysql files. 6.x and earlier versions have the files in /usr/local/mysql. Why is mysql even looking in /var/lib?? I remembered mention of similar problems on the list, so I did a search on the website, but I am turning up messages three years old, with commands like "UPDATE" that are not being recognized. Is there a way to fix this? Do I have to scratch again and start over in the /var/lib directory? I emailed the error files from my last attempt, but it disappeared. This time, the error file just filled with help messages. Do I have to reinstall Redhat with v.7 to make the current mysql release work? Do I have to scratch and use the previous version to make it work on v.6.1? Please help. I'm stumped and frustrated. John Jensen 520 Goshawk Court Bakersfield, CA 93309 661-833-2858 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: sth-execute - screen/file output
You are just missing a step. The execute method does exactly what it says,
executes the prepared SQL statement. Once this is done, you must fetch data
from the handle with one of the fetch methods such as fetchrow_array or
fetchall_arrayref. Another alternative is to combine the prepare, execute,
and fetch into a single statement with one of the operations on a database
handle such as $dbh-selectrow_array(sql statement), etc. There are a few
ways to actually fetch the data, I'd suggest taking a look at the
documentation.
Sean
-Original Message-
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Sunday, February 04, 2001 10:35 PM
Subject: sth-execute - screen/file output
hi list,
im trying to write a perl srcipt that will connect to a mysql database
server, do some queries and print the output on the screen (or maybe append
the output to a file), that would look something like this.
+--+---+--+-+
| tnum | user | cust | area|
+--+---+--+-+
| 22 | nivra | testing | isdn |
| 23 | nivra | testing1 | ddu |
| 24 | nivra | testing1 | ddu |
+--+---+--+-+
below is my perl script.
#!/usr/bin/perl
use DBI;
$dbname= "dbname";
$dbuser = "dbuser";
$dbpass = "dbpass";
$dbhost = "localhost";
$dbport = "3306";
$dsn = "DBI:mysql:database=$dbname;host=$dbhost;port=$dbport";
$condition = " where date = '2001/01/27' and petsa = '2001/01/31' and
user = 'user'";
# Connect to the database
$dbh = DBI-connect($dsn, $dbuser, $dbpass);
# if needed and execute the SELECT
$sth = $dbh-prepare("SELECT tnum, user, type, area, stat FROM
tickets$where ");
$output = $sth-execute;
# clean up disconnect from the DB
$sth-finish;
$dbh-disconnect;
print $output;
but it doesn't give me any output at all. i'd like to know if there is any
special parameter to use with sth-execute to do this. did i miss anything
here?
thanks for your time.
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: How to uninstall MySQL?
Just take the .rpm off the end, and any additional platform information like i386, etc. It would just be, for example, rpm -e MySQL-3.23.32-1 Sean On Fri, 2 Feb 2001, Abby Jiang wrote: Hi, I installed MySQL on Red Hat 6.2. Now I am having trouble with uninstalling it. If I do rpm -erase MySQL-version.rpm, the message saying "no rpm package is installed". If I do rpm -i MySQL-version.rpm, the message says that the rpm package is already installed. what should I do to uninstall it? Thanks! = Abby __ Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL server has gone away error
I posted a couple of days ago abou this error and got no response, so I am trying again with a bit more detail this time. I am running mysql 3.23.28-gamma on a pretty much stock RH 6.2 box. I am accessing the database using Perl CGI scripts and the DBI API. I have reset the max_allowed_packet and wait_timeout values to 10M and 32 hours respectively as is suggested in the manual, but this has had no effect. Here are the specifics from the error logs: DBD::mysql::st execute failed: MySQL server has gone away at /cgi-bin/common/utility.pl line 85. 010109 14:37:27 Aborted connection 265218 to db: '' user: '' host: `localhost' (Got timeout reading communication packets) 010109 14:37:27 /usr/local/libexec/mysqld: Shutdown Complete 010109 14:37:27 mysqld ended\n Sean Conley - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
