Restore database improve code


 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers Restore database improve code
# 1  
Old 04-21-2020
Quote:
Originally Posted by mustfirst
let me know if you can suggest any improvement in my code. I think i have too many ECHO.
.
.
.
Yes, definitely. After running this 10 times, you'll be fed up with its verbosity and scrap all the output except for error messages. *nix philosophy: no news is good news.
You may want to better structure your code. You've done some block building, yes, but e.g. indenting might improve readability and understandability for future you, and others.
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Improve awk code that has three separate parts

I have a very inefficient awk below that I need some help improving. Basically, there are three parts, that ideally, could be combined into one search and one output file. Thank you :). Part 1: Check if the user inputted string contains + or - in it and if it does the input is writting to a... (4 Replies)
Discussion started by: cmccabe
4 Replies

2. Programming

Improve the performance of my C++ code

Hello, Attached is my very simple C++ code to remove any substrings (DNA sequence) of each other, i.e. any redundant sequence is removed to get unique sequences. Similar to sort | uniq command except there is reverse-complementary for DNA sequence. The program runs well with small dataset, but... (11 Replies)
Discussion started by: yifangt
11 Replies

3. Solaris

Restore a database on solaris..

hi All, Can anyone help me with the set of commands which are used to restore maybe a sybase database on solaris.. (1 Reply)
Discussion started by: sankasu
1 Replies

4. AIX

mksysb restore - Wrong OS level for restore

Hi all, I am still working on my mksysb restore. My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored. 0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies
Login or Register to Ask a Question
MYSQL_DROP_DB(3)							 1							  MYSQL_DROP_DB(3)

mysql_drop_db - Drop (delete) a MySQL database

SYNOPSIS
Warning This function was deprecated in PHP 4.3.0, and will be removed in the future, along with the entirety of the original MySQL exten- sion. Instead, the MySQLi or PDO_MySQL extension should be used. See also MySQL: choosing an API guide and related FAQ for more information. Alternatives to this function include: oExecute a DROP DATABASE query bool mysql_drop_db (string $database_name, [resource $link_identifier = NULL]) DESCRIPTION
mysql_drop_db(3) attempts to drop (remove) an entire database from the server associated with the specified link identifier. This function is deprecated, it is preferable to use mysql_query(3) to issue an sql DROP DATABASE statement instead. o $database_name - The name of the database that will be deleted. o $ link_identifier -The MySQL connection. If the link identifier is not specified, the last link opened by mysql_connect(3) is assumed. If no such link is found, it will try to create one as if mysql_connect(3) was called with no arguments. If no connection is found or established, an E_WARNING level error is generated. Returns TRUE on success or FALSE on failure. Example #1 mysql_drop_db(3) alternative example <?php $link = mysql_connect('localhost', 'mysql_user', 'mysql_password'); if (!$link) { die('Could not connect: ' . mysql_error()); } $sql = 'DROP DATABASE my_db'; if (mysql_query($sql, $link)) { echo "Database my_db was successfully dropped "; } else { echo 'Error dropping database: ' . mysql_error() . " "; } ?> Warning This function will not be available if the MySQL extension was built against a MySQL 4.x client library. Note For backward compatibility, the following deprecated alias may be used: mysql_dropdb(3) mysql_query(3). PHP Documentation Group MYSQL_DROP_DB(3)