Path: utzoo!attcan!uunet!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!ucsd!helios.ee.lbl.gov!nosc!humu!pegasus!jkwood
From: jkwood@pegasus.com (Keith Wood)
Newsgroups: comp.databases
Subject: Re: flakey Obj-C/Sybase stuff
Message-ID: <1990Jun27.023244.4648@pegasus.com>
Date: 27 Jun 90 02:32:44 GMT
References: <1990Jun26.073113.682@pegasus.com>
Organization: Independent software developer
Lines: 24
X-Local-Date: 26 Jun 90 19:32:44 PDT

Well, the good news is that I found the problem on my own.  The bad news is that Sybase's error messages were rather misleading...

In my actual program listing the final column specification for fieldC did not have a space following it, so the command buffer thought that I was selecting fieldCfrom.

	dbcmd(dbproc, "select fieldA, ");
	dbcmd(dbproc, "fieldB, fieldC");       <--  problem is here
	dbcmd(dbproc, "from tableC ");
	dbcmd(dbproc, "where dataKey = -1");

Why sybase then decides to report EVERY COLUMN as an 'Invalid column name' is somewhat beyond me, but that's the case...

Editing out the <<dbcmd(dbproc, ">> and the <<");>> from the source file and pasting it back into the Shell running isql did not cause problems because isql treats a newline character as a space.

Adding a space to the line (fieldC ") brought everything right into alignment, and things work great...


Jeez, just another one of those things...

Keith Wood

<NeXT mail>		jkwood@manana.pegasus.com		
<NeXT mail>		next1!manana!jkwood@next.com
<Voice>			(808) 259-5234
<FAX>			(808) 259-5652