Re: New engines lack character based tools
Mark, this is not something I have checked out since, admittedly my SQL
statements that I use in the manner we have been discussing tend to be
simple and my error checking of the nature that if the return is zero, I go
on. If not, I quit. Any instance where I need more I code differently.
Like C or 4GL.
----------
} From: Mark Christmas <mchristmas@crosskeys.com>
} To: informix-list@rmy.emory.edu
} Subject: Re: New engines lack character based tools
} Date: Monday, March 03, 1997 11:20
}
} John Wells wrote:
} >
} > I am not sure what you are talking about here, but I write command line
sql
} > calls like this
} >
} > echo "select * from <some table> where <something = something>" |
dbaccess
} > dbname
} >} > I also put this in shell scripts in all sort sorts of ways and find it
very
} > useful.
} >
} > Read your dbaccess manual.
}
} John: yes this works for successful SQL statements, but how do you take
} this, wrap it in a script, and then look for the sql ret-code for each
} statement? This is where the problem is - you don't get an sql code, you
} get a generic 255 code.
} --
} +-----------------------------------------------+
} | Mark Christmas mchristmas@crosskeys.com
} | CrossKeys Systems Corp http://www.crosskeys.com
} | 350 Terry Fox Dr
} | Kanata, ON, Canada K2K 2W5
} | Phone (613) 591-1600 Fax (613) 599-3626
} +-----------------------------------------------+