Scott,
I don't much care for the weather here where I live, but I have to accept
it :-/
Same thing with SQL in MapInfo: it's an implemented subset, which has been
clear from the start.
And your "shortcoming" problem is actually easily solved using other also
standard SQL functionality,
so the request for improving MI Pro SQL is - in this case - like shooting
sparrows with cannons.
Select * From TableA Where ColumnY=5
Update Selection Set ColumnX=2
Qed.
No need to bang your head into the wall, just walk around it :-)
Lars Nielsen
**********************************************************
Lars Nielsen [EMAIL PROTECTED]
Development Manager, MapXtreme iGIS Specialist
Kampsax / MapInfo GIS, Odense http://www.mapinfo.dk
Authorized MapInfo Partner & Distributor in Denmark
Address: Rugaardsvej 55, DK-5000 Odense C
Telephone: +45 6313-5000 Facsimile +45 6313-5090
**********************************************************
"Scott Fagg" <[EMAIL PROTECTED]> on 06-06-2000 23:46:31
To: [EMAIL PROTECTED]
cc:
Subject: MI Shortcoming of MapInfo's SQL
I'm often frustrated by the poorly implemented SQL in mapinfo, for example,
the following straightforward SQL fails...
update TableA set ColumnX=2 where ColumnY=5
Isn't this a pretty basic SQL query?
Is anyone organizing a petition to convince the MapInfo developers to
implement a bit more of the SQL spec?
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
