On Thu, 28 Sep 2006, Griggs, Donald wrote:
Depending on your needs, if it's awkward to trim away the final delimiter,
you might choose to simply add a dummy field to your table.
Donald,
No, it's easy enough in joe to replace a space followed by the end-of-line
($) with just the end-of-line. This exercise was with a set of test data,
but I'll make sure that the real data have no trailing spaces when they're
inserted into the database.
It's the apparent lack of documentation on these subtle points that I
think need correcting. I wonder now how many more gotcha's are waiting to
trap me as a naive user.
Playing with the table data once it was available also taught me something
I did not anticipate. If the raw data file had the two text strings
deliminete by quotes ("xxx"), that's how they were entered in the table, and
it would have apparently taken double quotes in the where phrase of the
select statement to find them.
Specifically, when I tried this:
select * from voting where cat = "nat" and pos = "pro";
nothing was returned, while 'select * from voting' dumped all values to the
screen. Hmmm-m-m.
I deleted all the inserted records, removed the quotes from the two text
fields in the data file, and re-imported it. Now the first select statement
works. My inference is that the data file quotes became part of the string
as stored in the table, so the select statement would need to be
select * from voting where cat = ' "nat" ' and pos = ' "pro" ';
Awkward. Feh!
Thanks,
Rich
--
Richard B. Shepard, Ph.D. | The Environmental Permitting
Applied Ecosystem Services, Inc.(TM) | Accelerator
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
