public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Buchbinder, Barry (NIH/NIAID)" <BBuchbinder@niaid.nih.gov>
To: cygwin@cygwin.com
Subject: RE: Piping output from sqlplus
Date: Thu, 16 Dec 2004 21:33:00 -0000	[thread overview]
Message-ID: <F76C9B2DA2FC4C4CA0A18E288BBCBCF71026EC36@nihexchange24.nih.gov> (raw)

At Thursday, December 16, 2004 3:57 PM, Chuck wrote:
> 
> Buchbinder, Barry (NIH/NIAID) wrote:
>> At Thursday, December 16, 2004 3:29 PM, Chuck wrote:
>>> 
>>> I'm having a strange problem reading the output from sqlplus in
>>> Cygwin. Sqlplus is a windows command line program used to access
>>> oracle databases. My command looks something like this...
>>> 
>>> sqlplus -s <<! | read line
>>> user/password@database
>>> set pagesize 0 linesize 200 feedback off tab off
>>> select col1||chr(9)||col2
>>> from table;
>>> !
>>> 
>>> This should output one line to stdout with the two values separated
>>> by a tab character. The read command should read it into the
>>> variable $line. On my Solaris system it works perfectly. In Cygwin,
>>> $line is empty. 
>>> 
>>> If I remove the "read line", the output displays on the tty just
>>> fine. 
>>> 
>>> I though it might be related to the line end characters so I tried
>>> converting them with the dos2unix filter. Didn't work. Neither did
>>> tr -d \\r. Both ways, $line still ends up being empty.
>>> 
>>> If I replace the "read line" with "od -c" to dump the characters, it
>>> shows the one line as expected.
>>> 
>>> If I redirect the output to a file, the file contains one line as
>>> expected. 
>>> 
>>> If I try to read the output into a variable, I get an empty variable
>>> 
>>> Any ideas?
>> 
>> If the output shows up OK in a file, do
>> VAR="$(cat file)"
> 
> That may work but it misses the point. I'm writing a script and I want
> it to work on Cygwin and unix.
> 
> BTW the shell I'm using is ksh.

Well, I don't have access to a Unix or Linux machine, but I would have
thought outputting a file and filing the variable by cat'ting it would work
there, too.

I don't use ksh.  If what I suggested does not work there, something like
the following should.

VAR=`cat file`

If the trailing \n gets converted into an undesirable space, you could
always do

VAR=`cat file | tr -d '\n'`

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2004-12-16 21:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 21:33 Buchbinder, Barry (NIH/NIAID) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-17 20:59 Bakken, Luke
2004-12-20 15:25 ` Chuck
2004-12-20 16:15   ` Igor Pechtchanski
2004-12-20 16:43   ` Christopher Faylor
2004-12-21 16:42     ` Chuck
2004-12-16 21:36 Bakken, Luke
2004-12-17 12:59 ` Chuck
2004-12-17 13:06   ` Dave Korn
2004-12-17 16:26 ` Chuck
2004-12-17 16:35   ` Christopher Faylor
2004-12-17 20:17     ` Chuck
2004-12-16 20:48 Buchbinder, Barry (NIH/NIAID)
2004-12-16 21:11 ` Chuck
2004-12-16 20:29 Chuck
2004-12-16 20:39 ` Christopher Faylor
2004-12-16 21:19   ` Chuck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F76C9B2DA2FC4C4CA0A18E288BBCBCF71026EC36@nihexchange24.nih.gov \
    --to=bbuchbinder@niaid.nih.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).