Re: Informix vs Oracle vs DB2. SQL Query optimization.
> I think the reason > is that Oracle still has issues with derivative data types. (You call > them cartridges, IDS calls them datablades.) But then again,. my > client isn't your ordinary user of spatial data. To be clear here - cartridges are extensions to the Oracle server, in a fashion similar to Datablades in Informix. But Spatial (and the other native data types supported in Oracle) are not implemented as cartridges in the Oracle engine - they are data types supported by the kernel directly. They may have been implemented as cartridges in earlier releases, but over time have been bought into the fold (or died)
On Oct 12, 3:26 pm, Mark Townsend <markbtowns...@sbcglobal.net> wrote: > > I think the reason > > > is that Oracle still has issues with derivative data types. (You call > > them cartridges, IDS calls them datablades.) But then again,. my > > client isn't your ordinary user of spatial data. > > To be clear here - cartridges are extensions to the Oracle server, in a > fashion similar to Datablades in Informix. But Spatial (and the other > native data types supported in Oracle) are not implemented as cartridges > in the Oracle engine - they are data types supported by the kernel > directly. They may have been implemented as cartridges in earlier > releases, but over time have been bought into the fold (or died) Ah. So you're saying that spatial is now a native data type? That makes the issue worse. Sorry.
Ian Michael Gumby wrote: > On Oct 12, 3:26 pm, Mark Townsend <markbtowns...@sbcglobal.net> wrote: >> > I think the reason >> >>> is that Oracle still has issues with derivative data types. (You call >>> them cartridges, IDS calls them datablades.) But then again,. my >>> client isn't your ordinary user of spatial data. >> To be clear here - cartridges are extensions to the Oracle server, in a >> fashion similar to Datablades in Informix. But Spatial (and the other >> native data types supported in Oracle) are not implemented as cartridges >> in the Oracle engine - they are data types supported by the kernel >> directly. They may have been implemented as cartridges in earlier >> releases, but over time have been bought into the fold (or died) > > Ah. So you're saying that spatial is now a native data type? That > makes the issue worse. > Sorry. Only with respect to your profound ignorance which has again been pointed out. No doubt your next foray will be to tell us that interval data types should not be in the kernel. How about LOBs? -- Daniel A. Morgan University of Washington damorgan@x.washington.edu (replace x with u to respond)
On Oct 13, 12:43 am, DA Morgan <damor...@psoug.org> wrote: > Ian Michael Gumby wrote: > > On Oct 12, 3:26 pm, Mark Townsend <markbtowns...@sbcglobal.net> wrote: > >> > I think the reason > > >>> is that Oracle still has issues with derivative data types. (You call > >>> them cartridges, IDS calls them datablades.) But then again,. my > >>> client isn't your ordinary user of spatial data. > >> To be clear here - cartridges are extensions to the Oracle server, in a > >> fashion similar to Datablades in Informix. But Spatial (and the other > >> native data types supported in Oracle) are not implemented as cartridges > >> in the Oracle engine - they are data types supported by the kernel > >> directly. They may have been implemented as cartridges in earlier > >> releases, but over time have been bought into the fold (or died) > > > Ah. So you're saying that spatial is now a native data type? That > > makes the issue worse. > > Sorry. > > Only with respect to your profound ignorance which has again been > pointed out. No doubt your next foray will be to tell us that interval > data types should not be in the kernel. How about LOBs? > -- > Daniel A. Morgan > University of Washington > damor...@x.washington.edu (replace x with u to respond) Daniel, I deal with multiple versions of databases on a daily basis. Its difficult to keep on top of all of the little changes that occur over time. The fact that Mark said that the spatial data types are now no longer a derived data type doesn't make things look better for Oracle's spatial. Also it doesn't make sense. I seem to recall that talking with DBAs that you got Oracle spatial as part of Enterprise Edition, but not with the other editions. Of course some of the confusion is that these Oracle DBAs have been working with Oracle for years and as Mark points out. It wasn't until a recent release that they are now native. Is that 11 or 10g? See, you really should go back and teach your extended education class and leave the software development to the professionals. BTW, I don't consider myself a DBA since I'm not an engine jockey. I'll do the logical design and the app work but I'm not tied to the engine. -G
Ian Michael Gumby wrote: > Daniel, I deal with multiple versions of databases on a daily basis. > Its difficult to keep on top of all of the little changes that occur > over time. The fact that you "deal with multiple versions on a daily basis" is a strong indication to me that your skills are those of a generalist rather than a specialist. And that, in view of your previous posts, is being quite generous. > The fact that Mark said that the spatial data types are now no longer > a derived data type doesn't make things look better for Oracle's > spatial. You, of course, being an expert on the coding in the Oracle kernel with respect to how data types are defined and the implications thereof ... Or perhaps because of some objective testable fact ... Or because of the following? > Also it doesn't make sense. Which it seems is the actual issue that runs through this thread. -- Daniel A. Morgan University of Washington damorgan@x.washington.edu (replace x with u to respond)