StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to create a /usr/bin/mysql wrapper program via IO redirection?
primarykey
Id
1351491
data
AcceptedAnswerId
1351544
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-29T13:49:29.237
FavoriteCount
0
LastActivityDate
2009-08-29T14:19:36.060
LastEditDate
LastEditorUserId
0
OwnerUserId
125540
ParentId
0
PostTypeId
1
Score
0
ViewCount
668
LastEditorDisplayName
text
Body
Presently, I'm thoroughly dissatisfied by the command-line program /usr/bin/mysql! It does not, e.g., let me leverage: (a) various Unix tools (like, grep, sed...), and (b) Unix concepts such as io-redirection, piping. (Btw, IIRC, a command-line shell for Sybase used to allow piping and sufficiently powerful, Unix-style command-line usage.) So... I'm wondering, if it's possible to create a shell wrapper on my own for this sucker? My first version looks like this. <pre><code># #!/bin/bash sqlUser=USER_NAME sqlPassword= # The password will be taken from ~/.my.cnf . # Sql statements specified via stdin. while read -p 'SQL> ' x do if [ "$x" = "quit" ]; then # Quit the loop. echo "Goodbye." break else eval "mysql -u$sqlUser -e '$x' " echo fi done </code></pre> Sample usage: <pre><code>[sd@host:~/tmp] $ ./mysqlsh SQL> select * from bankdb.loan; +---------+---------------+--------+ | loan_no | branch_name | amount | +---------+---------------+--------+ | L-11 | Round Hill | 900 | | L-14 | Downtown | 1500 | | L-15 | Perryridge | 1500 | | L-16 | Perryridge | 1300 | | L-17 | Downtown | 1000 | | L-23 | Redwood | 2000 | | L-93 | Mianus | 500 | +---------+---------------+--------+ SQL> quit Goodbye. [sd@host:~/tmp] $ </code></pre> <ol> <li>Now, while I could add the piping/redirection feature by saying to myself that... anything preceding the semi-colon ';' in the user input to read() would be the SQL, and anything following the ';' would be the Unix shell constructs to be passed straight to eval() above. But, I'm not sure if this is the greatest way!</li> <li>Another very serious limitation that would still persist is: There will be no concept of a session... due to a new invocation of /usr/bin/mysql in every iteration of the while-loop. So, what I'd really like to be able to do is: (a) launch one, single instance of /usr/bin/mysql, and (b) somehow wire /usr/bin/mysql's stdin, stdout, stderr streams to my wrapper program's. Now, is this stunt possible? Note that I tried [sd@host:~/tmp] $ mysql -uSD 2>&1 | tee sql.out and it did not work as 'expected'. Meaning, I did not get the familiar mysql interactive messages to my sql.out file, so wondering what's going on here!!</li> <li>If this is not possible via shell (bash), could this be done via a C-program...? that uses MySQL's C API, say, to open a database connection and then provide a sense of session over this connection?</li> <li>Could Perl help here?</li> </ol> Many thanks for listening.
Tags
<mysql><command-line><wrapper>
Title
How to create a /usr/bin/mysql wrapper program via IO redirection?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USHarry
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.