SQL is a ANSI standard. Not Microsoft
-------------------------------------------------
Larry Simonsen Phone: 801-489-2450
Flowserve Corporation Fax: 801-491-1750
PO Box 2200 http://www.Flowserve.com
Springville, UT 84663 e-mail: [log in to unmask]
-------------------------------------------------
All opinions expressed herein are my own and reflect, in no way, those of my
employer.
-----Original Message-----
From: Johnson, Tracy [mailto:[log in to unmask]]
Sent: Friday, April 14, 2000 11:58 AM
To: [log in to unmask]
Subject: Re: ODBC
Yes I understand that ODBC is a SQL standard.
I also understand Microsoft wrote the SQL spec.
I also understand some vendor's ODBC drivers do more things
than the standard (such as HP's IMAGESQL, or Minisoft's, or
whoever's.) Each vendor is slightly different in their
methods.
That's why I mentioned it.
Tracy M. Johnson
TRW Automotive Electronics
Sensors & Components
-----Original Message-----
From: Kenhp3000-L [mailto:[log in to unmask]]
Sent: Friday, April 14, 2000 4:48 AM
To: [log in to unmask]
Subject: Re: ODBC
Tracy,
What you must understand is that ODBC is a SQL standard, and it is the SQL
language which precludes array handling as it does not include an index.
However IMAGESQL will AUTOSPLIT arrays into discrete items.
There is a limitation to the number of items allowed in a tuple (returned
row) which you may like to ask HP to expand, but if they did you may well
find that the PC application cannot handle the maximum currently permitted
presently.
If these issues impact upon you I suggest you get your votes in on the
ballot today.
http://www.csillc.com/sigs/
Ken Vickers
LINKWAY Development and Support
__________________________________
Computing Solutions Limited
Tel. +44 1905 794400
Fax. +44 1905 794464
mailto:[log in to unmask]
http://www.csllink.com
__________________________________
----- Original Message -----
From: Johnson, Tracy <[log in to unmask]>
To: <[log in to unmask]>
Sent: 13 April 2000 18:33
Subject: Re: ODBC
> There is an incompatability with some ODBC drivers
> to understand Image arrays, but heck, Image arrays
> are not "standard" SQL, so full compatability with
> the Microsoft spec of ODBC is not to be expected.
> I would think any user trying to force the issue is
> on their own, although any HP3000 ODBC vendor has to
> have a way of getting through this via their own
> extensions to the Microsoft spec of ODBC.
>
> For example: One unnamed vendor can handle Image
> arrays in their ODBC, but you can't index on any
> of those arrayed fields. (Not that I think any
> other vendor could do it either, so I'm happy
> as it is.) Besides most Image databases will have
> plenty of other non-arrayed fields to index on, so
> it should be that critical an issue.
>
> In another situation, the ODBC driver is not a problem,
> and Third Party Indexing (TPI) is not a problem either.
> But try and mix the two, and you "may" have problems.
>
> Tracy M. Johnson
> TRW Automotive Electronics
> Sensors & Components
>
>
> -----Original Message-----
> From: Mike Moncrieff [mailto:[log in to unmask]]
> Sent: Wednesday, April 12, 2000 3:43 PM
> To: [log in to unmask]
> Subject: ODBC
>
>
> Anyone had good experiences, horror stories to tell about using the
> available ODBC drivers for IMAGE
>
> Mike Moncrieff
|
