Abstract
no, this chapter is not about thinning the fat rows out of your cursors—which might not be a bad idea. It is about using the ADO Shape syntax to manage hierarchical data. But what is “hierarchical” data? Most of us work with hierarchical data most of the time without knowing it. For instance, when you work with a Customers table that is tied to an associated Invoices table, which has an associated Items table, that’s a hierarchy. The difference between a normal query and a hierarchical query is that the relationships are embedded in the hierarchy. That is, the schema of the relationship is part of the hierarchical structure. This way, the tool used to reference the data “knows” that there can be from zero to n orders for each customer and the Order table’s CustID should point back to a valid row in the Customers table.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2000 Apress
About this chapter
Cite this chapter
Vaughn, W.R. (2000). Getting Your Data into Shape. In: ADO Examples and Best Practices. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-1156-3_10
Download citation
DOI: https://doi.org/10.1007/978-1-4302-1156-3_10
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-893115-16-3
Online ISBN: 978-1-4302-1156-3
eBook Packages: Springer Book Archive