![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
-----Original Message----- From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info- ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Roy Hann Sent: 23 May 2011 11:26 To: info-ingres (AT) kettleriverconsulting (DOT) com Subject: [Info-Ingres] From "You learn something new everyday" file Or not. I just encountered the term "covering index" for the first time today. It was being put forth as an amazing and important DBMS feature that "everyone expects". I was obviously worried because I've never seen Ingres claim to implement covering indices or even express any aspiration to support them in future (whatever they are). I was even more worried 'cos I didn't know what they are and I suddenly felt left behind by technology. So I did a quick Google and found out Ingres has *always* supported them. It's just an expensive-sounding name for a secondary index with redundant data columns that can be used to satisfy a query without reference to the base table! Talk about calling a spade a pedolith agitator... -- Roy UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011. Register at http://www.regonline.co.uk/ukiua2011 _______________________________________________ Info-Ingres mailing list Info-Ingres (AT) kettleriverconsulting (DOT) com http://ext-cando.kettleriverconsulti...fo/info-ingres |
#4
| |||
| |||
|
|
Reminds me of when Oracle introduced this wonderful new feature "Index Organized Tables". When reading some blurb about it took me a moment to realise all they'd done was implement BTree tables. -----Original Message----- From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info- ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Roy Hann Sent: 23 May 2011 11:26 To: info-ingres (AT) kettleriverconsulting (DOT) com Subject: [Info-Ingres] From "You learn something new everyday" file Or not. I just encountered the term "covering index" for the first time today. It was being put forth as an amazing and important DBMS feature that "everyone expects". I was obviously worried because I've never seen Ingres claim to implement covering indices or even express any aspiration to support them in future (whatever they are). I was even more worried 'cos I didn't know what they are and I suddenly felt left behind by technology. So I did a quick Google and found out Ingres has *always* supported them. It's just an expensive-sounding name for a secondary index with redundant data columns that can be used to satisfy a query without reference to the base table! Talk about calling a spade a pedolith agitator... -- Roy |

).
#5
| |||
| |||
|
#6
| |||
| |||
|
|
it's like rules...others call it 'triggers' while Ingres calls it 'rules'. or MVCC called 'snapshot isolation' by SQL server etc. but there is no Ingres term for 'defered constraints' ...while at it,are we going to get deferred constraints same day in the future? |
#7
| |||
| |||
|
|
nikosv wrote: [clip] The show-stopper is that even products that support deferred constraints find relatively few customers use them. [clip] |
#8
| ||||
| ||||
|
|
On May 23, 2011, at 2:10 PM, Roy Hann wrote: nikosv wrote: [clip] The show-stopper is that even products that support deferred constraints find relatively few customers use them. [clip] Really? |
|
I use them all the time in Oracle with complex object hierarchies combined with Hibernate object-relational mapping. |
|
ORMs are famous for inserting rows out of order in complex transactions. |
|
I have seen teams purposely avoid putting constraints on their tables to avoid the problem. That just makes me sad. |
![]() |
| Thread Tools | |
| Display Modes | |
| |