"revdberr, " as the returned value on *successful* postgres operations

[Peter Haworth]

I guess I was looking for the Livecode script, not the SQL statement.  But
Mike's point is a good one; the dictionary is pretty adamant about not
including a semicolon at the end SQL statements

Pete
lcSQL Software <http://www.lcsql.com>


On Mon, May 13, 2013 at 6:52 PM, Dr. Hawkins <dochawk at gmail.com> wrote:

> On Mon, May 13, 2013 at 6:41 PM, Peter Haworth <pete at lcsql.com> wrote:
>
> > I haven't used LC with postgresql but seems pretty unlikely that a
> > successful operation would return "revdberr".  If you post your code and
> > also the full text of the error message you get back, can probably figure
> > out what's going on.
> >
>
> That's the problem--this *is* the entire result.
>
> Something like
>    UPDATE mytable SET mypet='cat' WHERE food='mice';
>
> yields this error
>
> But then checking
>    SELECT * FROM mytable;
>
> yields
>   cat <delim> mice
>
> where there was a prior entry of "snake, mice"
>
> I've seen this message many, many times, and every time I've checked the db
> contents when getting this one-word error, the commit was successful.
>
> It's as if LC has a structure
>
> SWITCH
>   CASE lots
>   CASE of
>   CASE conditions
>      put somenumber into theRes
>      break
>   DEFAULT
>       put "revdberr," into theRes
>       SWITCH
>           CASE condition 1;
>           put cr & gizmo after theRes
>           break
>        ...
>       <no DEFAULT CASE in embedded
>      END SWITCH
> END SWITCH
>
> return theRes
>
>
> .But I absolutely agree that it makes no sense . . .
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>