NAME
SQL::Routine::Details - Main structural and API documentation for SQL::Routine
COPYRIGHT AND LICENSE
This file is part of the SQL::Routine database portability library.
SQL::Routine is Copyright (c) 2002-2005, Darren R. Duncan. All rights reserved. Address comments, suggestions, and bug reports to perl@DarrenDuncan.net, or visit http://www.DarrenDuncan.net/ for more information.
SQL::Routine is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation (http://www.fsf.org/); either version 2 of the License, or (at your option) any later version. You should have received a copy of the GPL as part of the SQL::Routine distribution, in the file named "GPL"; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
Linking SQL::Routine statically or dynamically with other modules is making a combined work based on SQL::Routine. Thus, the terms and conditions of the GPL cover the whole combination. As a special exception, the copyright holders of SQL::Routine give you permission to link SQL::Routine with independent modules, regardless of the license terms of these independent modules, and to copy and distribute the resulting combined work under terms of your choice, provided that every copy of the combined work is accompanied by a complete copy of the source code of SQL::Routine (the version of SQL::Routine used to produce the combined work), being distributed under the terms of the GPL plus this exception. An independent module is a module which is not derived from or based on SQL::Routine, and which is fully useable when not linked to SQL::Routine in any form.
Any versions of SQL::Routine that you modify and distribute must carry prominent notices stating that you changed the files and the date of any changes, in addition to preserving this original copyright notice and other credits. SQL::Routine is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
While it is by no means required, the copyright holders of SQL::Routine would appreciate being informed any time you create a modified version of SQL::Routine that you are willing to distribute, because that is a practical way of suggesting improvements to the standard version.
DESCRIPTION
This POD file contains most of the core detail documentation for SQL::Routine, such as its function and method descriptions. You should read the summary introduction in SQL::Routine before this document and then read SQL::Routine::Language either concurrently to or after this document.
MATTERS OF PORTABILITY AND FEATURES
SQL::Routines are intended to represent all kinds of SQL, both DML and DDL, both ANSI standard and RDBMS vendor extensions. Unlike basically all of the other SQL generating/parsing modules I know about, which are limited to basic DML and only support table definition DDL, this class supports arbitrarily complex select statements, with composite keys and unions, and calls to stored functions; this class can also define views and stored procedures and triggers. Some of the existing modules, even though they construct complete SQL, will take/require fragments of SQL as input (such as "where" clauses) By contrast, SQL::Routine takes no SQL fragments. All of its inputs are atomic, which means it is also easier to analyse the objects for implementing a wider range of functionality than previously expected; for example, it is much easier to analyse any select statement and generate update/insert/delete statements for the virtual rows fetched with it (a process known as updateable views).
Considering that each database product has its own dialect of SQL which it implements, you would have to code SQL differently depending on which database you are using. One common difference is the syntax for specifying an outer join in a select query. Another common difference is how to specify that a table column is an integer or a boolean or a character string. Moreover, each database has a distinct feature set, so you may be able to do tasks with one database that you can't do with another. In fact, some databases don't support SQL at all, but have similar features that are accessible thorough alternate interfaces. SQL::Routine is designed to represent a normalized superset of all database features that one may reasonably want to use. "Superset" means that if even one database supports a feature, you will be able to invoke it with this class. You can also reference some features which no database currently implements, but it would be reasonable for one to do so later. "Normalized" means that if multiple databases support the same feature but have different syntax for referencing it, there will be exactly one way of referring to it with SQL::Routine. So by using this class, you will never have to change your database-using code when moving between databases, as long as both of them support the features you are using (or they are emulated). That said, it is generally expected that if a database is missing a specific feature that is easy to emulate, then code which evaluates SQL::Routines will emulate it (for example, emulating "left()" with "substr()"); in such cases, it is expected that when you use such features they will work with any database. For example, if you want a model-specified BOOLEAN data type, you will always get it, whether it is implemented on a per-database-basis as a "boolean" or an "int(1)" or a "number(1,0)". Or a model-specified "STR_CHAR" data type you will always get it, whether it is called "text" or "varchar2" or "sql_varchar".
SQL::Routine is intended to be just a stateless container for database query or schema information. It does not talk to any databases by itself and it does not generate or parse any SQL; rather, it is intended that other third party modules or code of your choice will handle this task. In fact, SQL::Routine is designed so that many existing database related modules could be updated to use it internally for storing state information, including SQL generating or translating modules, and schema management modules, and modules which implement object persistence in a database. Conceptually speaking, the DBI module itself could be updated to take SQL::Routine objects as arguments to its "prepare" method, as an alternative (optional) to the SQL strings it currently takes. Code which implements the things that SQL::Routine describes can do this in any way that they want, which can mean either generating and executing SQL, or generating Perl code that does the same task and evaling it, should they want to (the latter can be a means of emulation). This class should make all of that easy.
SQL::Routine is especially suited for use with applications or modules that make use of data dictionaries to control what they do. It is common in applications that they interpret their data dictionaries and generate SQL to accomplish some of their work, which means making sure generated SQL is in the right dialect or syntax, and making sure literal values are escaped correctly. By using this module, applications can simply copy appropriate individual elements in their data dictionaries to SQL::Routine properties, including column names, table names, function names, literal values, host parameter names, and they don't have to do any string parsing or assembling.
Now, I can only imagine why all of the other SQL generating/parsing modules that I know about have excluded privileged support for more advanced database features like stored procedures. Either the authors didn't have a need for it, or they figured that any other prospective users wouldn't need it, or they found it too difficult to implement so far and maybe planned to do it later. As for me, I can see tremendous value in various advanced features, and so I have included privileged support for them in SQL::Routine. You simply have to work on projects of a significant size to get an idea that these features would provide a large speed, reliability, and security savings for you. Look at many large corporate or government systems, such as those which have hundreds of tables or millions of records, and that may have complicated business logic which governs whether data is consistent/valid or not. Within reasonable limits, the more work you can get the database to do internally, the better. I believe that if these features can also be represented in a database-neutral format, such as what SQL::Routine attempts to do, then users can get the full power of a database without being locked into a single vendor due to all their investment in vendor-specific SQL stored procedure code. If customers can move a lot more easily, it will help encourage database vendors to keep improving their products or lower prices to keep their customers, and users in general would benefit. So I do have reasons for trying to tackle the advanced database features in SQL::Routine.
STRUCTURE
The internal structure of a SQL::Routine object is conceptually a cross between an XML DOM and an object-relational database, with a specific schema. This module is implemented with two main classes that work together, Containers and Nodes. The Container object is an environment or context in which Node objects usually live. A typical application will only need to create one Container object (returned by the module's 'new_container' function), and then a set of Nodes which live within that Container. The Nodes are related sometimes with single or multiple cardinality to each other.
SQL::Routine is expressly designed so that its data is easy to convert between different representations, mainly in-memory data structures linked by references, and multi-table record sets stored in relational databases, and node sets in XML documents. A Container corresponds to an XML document or a complete database, and each Node corresponds to an XML node or a database record. Each Node has a specific node_type (a case-sensitive string), which corresponds to a database table or an XML tag name. See the SQL::Routine::Language documentation file to see which ones exist. The node_type is set when the Node is created and it can not be changed later.
A Node has a specific set of allowed attributes that are determined by the node_type, each of which corresponds to a database table column or an XML node attribute. Every Node has a unique 'id' attribute (a positive integer) by which it is primarily referenced; that attribute corresponds to the database table's single-column primary key, with the added distinction that every primary key value in each table is distinct from every primary key value in every other table. Each other Node attribute is either a scalar value of some data type, or an enumerated value, or a reference to another Node of a specific node_type, which has a foreign-key constraint on it; those 3 attribute types are referred to respectively as "literal", "enumerated", and "Node-ref". Foreign-key constraints are enforced by this module, so you will have to add Nodes in the appropriate order, just as when adding records to a database. Any Node which is referenced in an attribute (cited in a foreign-key constraint) of another is a parent of the other; as a corollary, the second Node is a child of the first. The order of child Nodes under a parent is the same as that in which the parent-child relationship was assigned, unless you have afterwards used the move_before_sibling() method to change this.
The order of child Nodes under a parent is often significant, so it is important to preserve this sequence explicitly if you store a Node set in an RDBMS, since databases do not consider record order to be significant or worth remembering; you would add extra columns to store sequence numbers. You do not have to do any extra work when storing Nodes in XML, however, because XML does consider node order to be significant and will preserve it.
When the terms "parent" and "child" are used by SQL::Routine in regards to the relationships between Nodes, they are used within the context that a given Node can have multiple parent Nodes; a given Node X is the parent of another given Node Y because a Node-ref attribute of Node Y points to Node X. Another term, "primary parent", refers to the parent Node of a given Node Z that is referenced by Z's "pp" Node-ref attribute, which most Node types have. When SQL::Routines are converted to a purely hierarchical or tree representation, such as to XML, the primary parent Node becomes the single parent XML node. For example, the XML parent of a 'routine_var' Node is always a 'routine' Node, even though a 'scalar_domain' Node may also be referenced. Nodes of a few types, such as 'view_expr', can have primary parent Nodes that are of the same Node type, and can form trees of their own type; however, Nodes of most types can only have Nodes of other types as their primary parents.
Some Node types do not have a "pp" attribute and Nodes of those types never have primary parent Nodes; rather, all Nodes of those types will always have a specific pseudo-Node as their primary parents; pseudo-Node primary parents are not referenced in any attribute, and they can not be changed. All 6 pseudo-Nodes have no attributes, even 'id', and only one of each exists; they are created by default with the Container they are part of, forming the top 2 levels of the Node tree, and can not be removed. They are: 'root' (the single level-1 Node which is parent to the other pseudo-Nodes but no normal Nodes), 'elements' (parent to 'scalar_data_type' and 'row_data_type' and 'external_cursor' Nodes), 'blueprints' (parent to 'catalog' and 'application' Nodes), 'tools' (parent to 'data_storage_product' and 'data_link_product' Nodes), 'sites' (parent to 'catalog_instance' and 'application_instance' Nodes), and 'circumventions' (parent to 'sql_fragment' nodes). All other Node types have normal Nodes as primary parents.
You should look at the POD-only file named SQL::Routine::Language, which comes with this distribution. It serves to document all of the possible Node types, with attributes, constraints, and allowed relationships with other Node types. As the SQL::Routine class itself has very few properties and methods, all being highly generic (much akin to an XML DOM), the POD of this PM file will only describe how to use said methods, and will not list all the allowed inputs or constraints to said methods. With only simple guidance in Routine.pm, you should be able to interpret Language.pod to get all the nitty gritty details. You should also look at the tutorial or example files which will be in the distribution when ready. You could also learn something from the code in or with other modules which sub-class or use this one.
FAULT TOLERANCE AND MULTI-THREADING SUPPORT
Disclaimer: The following claims assume that only this module's published API is used, and that you do not set object properties directly or call private methods, which Perl 5 does not prevent. It also assumes that the module is bug free, and that any errors or warnings which appear while the code is running are thrown explicitly by this module as part of its normal functioning.
SQL::Routine is designed to ensure that the objects it produces are always internally consistent, and that the data they contain is always well-formed, regardless of the circumstances in which it is used. You should be able to fetch data from the objects at any time and that data will be self-consistent and well-formed.
This will not change regardless of what kind of bad input data you provide to object methods or module functions. Providing bad input data will cause the module to throw an exception; if you catch this and the program continues running (such as to chide the user and have them try entering correct input), then the objects will remain un-corrupted and able to accept new input or give proper output. In most cases, the object will be in the same state as it was before the public method was called with the bad input.
Note that, while SQL::Routine objects are always internally consistent, that doesn't mean that the data they store is always correct. Only the most critical kinds of input validation, constantly applied constraints, are done prior to storing or altering the data. Many kinds of data validation, deferrable constraints, are only done as a separate stage following its input; you apply those explicitly by invoking assert_deferrable_constraints(). One reason for the separation is to avoid spurious exceptions such as 'mandatory attribute not set' while a Node is in the middle of being created piecemeal, such as when it is storing details gathered one at a time from the user; another reason is performance efficiency, to save on a lot of redundant computation.
This module does not use package variables at all, besides constants like $VERSION, and all symbols ($@%) declared at file level are strictly constant value declarations. No object should ever step on another.
SQL::Routine is explicitly not thread-aware (thread-safe); it contains no code to synchronize access to its objects' properties, such as semaphores or locks or mutexes. To internalize such things in an effective manner would have made the code a lot more complex than it is now, without any clear benefits. However, this module can (and should) be used in multi-threaded environments where the application/caller code takes care of synchronizing access to its objects, especially if the application uses coarse-grained read or write locks.
The author's expectation is that this module will be mainly used in circumstances where the majority of actions are reads, and there are very few writes, such as with a data dictionary; perhaps all the writes on an object may be when it is first created. An application thread would obtain a read lock/semaphore on a Container object during the period for which it needs to ensure read consistency; it would block write lock attempts but not other read locks. It would obtain a write lock during the (usually short) period it needs to change something, which blocks all other lock attempts (for read or write).
An example of this is a web server environment where each page request is being handled by a distinct thread, and all the threads share one SQL::Routine object; normally the object is instantiated when the server starts, and the worker threads then read from it for guidance in using a common database. Occasionally a thread will want to change the object, such as to correspond to a simultaneous change to the database schema, or to the web application's data dictionary that maps the database to application screens. Under this situation, the application's definitive data dictionary (stored partly or wholly in a SQL::Routine) can occupy one place in RAM visible to all threads, and each thread won't have to keep looking somewhere else such as in the database or a file to keep up with the definitive copy. (Of course, any *changes* to the in-memory data dictionary should see a corresponding update to a non-volatile copy, like in an on-disk database or file.)
Note that, while a nice thing to do may be to manage a course-grained lock in SQL::Routine, with the caller invoking lock_to_read() or lock_to_write() or unlock() methods on it, Perl's thread->lock() mechanism is purely context based; the moment lock_to_...() returns, the object has unlocked again. Of course, if you know a clean way around this, I would be happy to hear it.
NODE IDENTITY ATTRIBUTES
Every Node has a positive integer 'id' attribute whose value is distinct among every Node in the same Container, without regard for the Node type. These 'id' attributes are used internally by SQL::Routine when linking child and parent Nodes, but they have no use at all in any SQL statement strings that are generated for a typical database engine. Rather, SQL::Routine defines a second, "surrogate id" ("SI") attribute for most Node types whose value actually is used in SQL statement strings, and corresponds to the SQL:2003 concept of a "SQL identifier" (such as a table name or a table column name). This attribute name varies by the Node type, but always looks like "si_*"; at least half of the time, the exact name is "si_name". If the SI attribute of a given Node is a literal or enumerated attribute, then its value is used directly for SQL strings; if it is a Node-ref attribute, then the SI attribute of the Node that it points to is used likewise for SQL strings in place of the given Node (this will recurse until we hold a Node whose SI attribute is not a Node-ref). In this way, SQL::Routine stores the "SQL identifier" value of each Node exactly once, and if it is edited then all SQL references to it automatically update.
To make SQL::Routine easier to use in the common cases, this module will treat all Node types as having a surrogate id attribute. In the few cases where a Node type has no distinct attribute for it (such as "view_expr" Nodes), this module will automatically use the 'id' (Node Id) attribute instead.
When the surrogate identifier attribute of a single Node is referenced on its own, this corresponds to the SQL:2003 concept of an "unqualified identifier". Under trivial circumstances, a Node can only be referenced by another Node using the former's unqualified identifier if either the first Node is a member of the second Node's primary-parent chain, or the first Node is a sibling of any member of said pp chain, or the first node has a pseudo-Node primary parent.
SQL::Routine implements context sensitive constraints for what values a given Node's surrogate identifier can have, and in what contexts other Nodes must be located wherein it is valid for them to link to the given Node and be its children; these go beyond the earlier-applied, more basic constraints that restrict parent-child connections based on the Node types and/or presence in the same Container of the Nodes involved. The rules for SI values are similar to the rules in typical programming languages concerning the declaration of variables and the scope in which they are visible to be referenced. One constraint is that all Nodes which share the same primary parent Node or pseudo-Node must have distinct SI values with respect to each other, regardless of Node type (eg, all columns and indexes in a table must have distinct names). Another constraint is described for general circumstances that in order for one given Node to reference another as its parent Node, that other Node must be either belong to the given Node's primary-parent chain, or it must be a direct sibling of either the given Node or a Node in its primary-parent chain, or it must be a primary-child of one of the primary parent Node's parent Nodes.
NOTE THAT FURTHER DOCUMENTATION ABOUT LINKING BY SURROGATE IDS IS PENDING.
SYNTAX
This class does not export any functions or methods, so you need to call them using object notation. This means using Class->function() for functions and $object->method() for methods. If you are inheriting this class for your own modules, then that often means something like $self->method().
All SQL::Routine functions and methods are either "getters" (which read and return or generate values but do not change the state of anything) or "setters" (which change the state of something but do not return anything on success); none do getting or setting conditionally based on their arguments. While this means there are more methods in total, I see this arrangement as being more stable and reliable, plus each method is simpler and easier to understand or use; argument lists and possible return values are also less variable and more predictable.
All "setter" functions or methods which are supposed to change the state of something will throw an exception on failure (usually from being given bad arguments); on success, they officially have no return values. A thrown exception will always include details of what went wrong (and where and how) in a machine-readable (and generally human readable) format, so that calling code which catches them can recover gracefully. The methods are all structured so that they check all preconditions prior to changing any state information, and so one can assume that upon throwing an exception, the Node and Container objects are in a consistent or recoverable state at worst, and are completely unchanged at best.
All "getter" functions or methods will officially return the value or construct that was asked for; if said value doesn't (yet or ever) exist, then this means the Perl "undefined" value. When given bad arguments, generally this module's "information" functions will return the undefined value, and all the other functions/methods will throw an exception like the "setter" functions do.
Generally speaking, if SQL::Routine throws an exception, it means one of two things: 1. Your own code is not invoking it correctly, meaning you have something to fix; 2. You have decided to let it validate some of your input data for you (which is quite appropriate).
Note also that SQL::Routine is quite strict in its own argument checking, both for internal simplicity and robustness, and so that code which *reads* data from it can be simpler. If you want your own program to be more liberal in what input it accepts, then you will have to bear the burden of cleaning up or interpreting that input, or delegating such work elsewhere. (Or perhaps someone may want to make a wrapper module to do this?)
CONSTRUCTOR WRAPPER FUNCTIONS
These functions are stateless and can be invoked off of either the module name, or any package name in this module, or any object created by this module; they are thin wrappers over other methods and exist strictly for convenience.
new_container()
my $model = SQL::Routine->new_container();
my $model2 = SQL::Routine::Container->new_container();
my $model3 = SQL::Routine::Node->new_container();
my $model4 = $model->new_container();
my $model5 = $node->new_container();This function wraps SQL::Routine::Container->new().
new_node( CONTAINER, NODE_TYPE[, NODE_ID] )
my $node = SQL::Routine->new_node( $model, 'table' );
my $node2 = SQL::Routine::Container->new_node( $model, 'table' );
my $node3 = SQL::Routine::Node->new_node( $model, 'table', 32 );
my $node4 = $model->new_node( $model, 'table', 45 );
my $node5 = $node->new_node( $model, 'table' );This function wraps SQL::Routine::Node->new( CONTAINER, NODE_TYPE, NODE_ID ).
CONTAINER CONSTRUCTOR FUNCTIONS AND METHODS
This function/method is stateless and can be invoked off of either the Container class name or an existing Container object, with the same result.
new()
my $model = SQL::Routine::Container->new();
my $model2 = $model->new();This "getter" function/method will create and return a single SQL::Routine::Container (or subclass) object.
CONTAINER OBJECT METHODS
These methods are stateful and may only be invoked off of Container objects.
is_read_only([ NEW_VALUE ])
This method returns this Container's "is read only" boolean property; if NEW_VALUE is defined, it will first set that property to it. When this flag is true, any attempt to modify this Container's Nodes (or most other Container properties) and/or add/remove Nodes will throw an exception. Only 2 properties of a read-only Container may validly be changed, which are "is read only" itself (setting to false) and "deferrable constraints are tested" (setting to true). The use of this feature helps to detect and prevent changes that are occurring after the time you expect model population to be completed.
auto_assert_deferrable_constraints([ NEW_VALUE ])
This method returns this Container's "auto assert deferrable constraints" boolean property; if NEW_VALUE is defined, it will first set that property to it. When this flag is true, SQL::Routine's build_*() methods will automatically invoke assert_deferrable_constraints() on the newly created Node, if it is in this Container, prior to returning it. The use of this method helps isolate bad input bugs faster by flagging them closer to when they were created; it is especially useful with the build*tree() methods.
auto_set_node_ids([ NEW_VALUE ])
This method returns this Container's "auto set node ids" boolean property; if NEW_VALUE is defined, it will first set that property to it. When this flag is true, SQL::Routine will automatically generate and set a Node Id for a Node that lacks one as soon as there is an attempt to put that Node in this Container. When this flag is false, a missing Node Id will cause an exception to be raised instead.
may_match_surrogate_node_ids([ NEW_VALUE ])
This method returns this Container's "may match surrogate node ids" boolean property; if NEW_VALUE is defined, it will first set that property to it. When this flag is true, SQL::Routine will accept a wider range of input values when setting Node ref attribute values, beyond Node object references and integers representing Node ids to look up; if other types of values are provided, SQL::Routine will try to look up Nodes based on other attributes than the Id, usually 'si_name', before giving up on finding a Node to link.
delete_node_tree()
This "setter" method will delete all of the Nodes in this Container. The semantics are like invoking delete_node() on every Node in the appropriate order, except for being a lot faster.
get_child_nodes([ NODE_TYPE ])
my $ra_node_list = $model->get_child_nodes();
my $ra_node_list = $model->get_child_nodes( 'catalog' );This "getter" method returns a list of this Container's primary-child Nodes, in a new array ref. A Container's primary-child Nodes are defined as being all Nodes in the Container whose Node Type defines them as always having a pseudo-Node parent. If the optional argument NODE_TYPE is defined, then only child Nodes of that Node Type are returned; otherwise, all child Nodes are returned. All Nodes are returned in the same order they were added.
find_node_by_id( NODE_ID )
my $node = $model->find_node_by_id( 1 );This "getter" method searches for a member Node of this Container whose Node Id matches the NODE_ID argument; if one is found then it is returned by reference; if none is found, then undef is returned. Since SQL::Routine guarantees that all Nodes in a Container have a distinct Node Id, there will never be more than one Node returned. The speed of this search is also very fast, and takes the same amount of time regardless of how many Nodes are in the Container.
find_child_node_by_surrogate_id( TARGET_ATTR_VALUE )
my $data_type_node = $model->find_child_node_by_surrogate_id( 'str100' );This "getter" method searches for a Node in this Container whose Surrogate Node Id matches the TARGET_ATTR_VALUE argument; if one is found then it is returned by reference; if none is found, then undef is returned. The TARGET_ATTR_VALUE argument is treated as an array-ref; if it is in fact not one, that single value is used as a single-element array. The search is multi-generational, one generation more childwards per array element. If the first array element is undef, then we assume it follows the format that Node.get_surrogate_id_chain() outputs; the first 3 elements are [undef,'root',<l2-psn>] and the 4th element matches a Node that has a pseudo-Node parent. If the first array element is not undef, we treat it as the aforementioned 4th element. If a valid <l2-psn> is extracted, then only child Nodes of that pseudo-Node are searched; otherwise, the child Nodes of all pseudo-Nodes are searched.
get_next_free_node_id()
my $node_id = $model->get_next_free_node_id();This "getter" method returns an integer which is valid for use as the Node ID of a new Node that is going to be put in this Container. Its value is 1 higher than the highest Node ID for any Node that is already in the Container, or had been before; in a brand new Container, its value is 1. You can use this method like a sequence generator to produce Node Ids for you rather than you producing them in some other way. An example situation when this method might be useful is if you are building a SQL::Routine by scanning the schema of an existing database. This property will never decrease in value during the life of the Container, and it can not be externally edited.
get_edit_count()
my $count_sample = $model->get_edit_count();This "getter" method will return the integral "edit count" property of this Container, which counts the changes to this Container's Node set. Its value starts at zero in a brand new Container, and is incremented by 1 each time a Node is edited in, added to, or deleted from the Container. The actual value of this property isn't important; rather the fact that it did or didn't change between two arbitrary samplings is what's important; it lets the sampler know that something changed since the previous sample was taken. This property will never decrease in value during the life of the Container, and it can not be externally edited. This feature is designed to assist external code that caches information derived from a SQL::Routine model, such as generated SQL strings or Perl closures, so that it can easily tell when the cache may have become stale (leading to a cache flush).
deferrable_constraints_are_tested()
my $is_all_ok = $model->deferrable_constraints_are_tested();This "getter" method returns true if, following the last time this Container's Node set was edited, the Container.assert_deferrable_constraints() method had completed all of its tests without finding any problems (meaning that all Nodes in this Container are known to be free of all data errors, both individually and collectively); this method returns false if any of the tests failed, or the test suite was never run (including with a new empty Container, since a Container completely devoid of Nodes may violate a deferrable constraint).
assert_deferrable_constraints()
$model->assert_deferrable_constraints();This "getter" method implements several types of deferrable data validation, to make sure that every Node in this Container is ready to be used, both individually and collectively; it throws an exception if it can find anything wrong. Note that a failure with any one Node will cause the testing of the whole set to abort, as the offending Node throws an exception which this method doesn't catch; any untested Nodes could also have failed, so you will have to re-run this method after fixing the problem. This method will short-circuit and not perform any tests if this Container's "deferrable constraints are tested" property is equal to its "edit count" property, so to avoid unnecessary repeated tests due to redundant external invocations; this allows you to put validation checks for safety everywhere in your program while avoiding a corresponding performance hit. This method will update "deferrable constraints are tested" to match "edit count" when all tests pass; it isn't updated at any other time.
NODE CONSTRUCTOR FUNCTIONS AND METHODS
This function/method is stateless and can be invoked off of either the Node class name or an existing Node object, with the same result.
new( CONTAINER, NODE_TYPE[, NODE_ID] )
my $node = SQL::Routine::Node->new( $model, 'table' );
my $node2 = SQL::Routine::Node->new( $model, 'table', 27 );
my $node3 = $node->new( $model, 'table' );
my $node4 = $node->new( $model, 'table', 42 );This "getter" function/method will create and return a single SQL::Routine::Node (or subclass) object that lives in the Container object given in the CONTAINER argument; the new Node will live in that Container for its whole life; if you want to conceptually move it to a different Container, you must clone the Node and then delete the old one. The Node Type of the new Node is given in the NODE_TYPE (enum) argument, and it can not be changed for this Node later; only specific values are allowed, which you can see in the SQL::Routine::Language documentation file. The Node Id can be explicitly given in the NODE_ID (uint) argument, which is a mandatory argument unless the host Container has a true "auto set node ids" property, in which case a Node Id will be generated from a sequence if the argument is not given. All of the Node's other properties are defaulted to an "empty" state.
NODE OBJECT METHODS
These methods are stateful and may only be invoked off of Node objects.
delete_node()
This "setter" method will destroy the Node object that it is invoked from, if it can; it does this by clearing all references between this Node and its parent Nodes and its Container, whereby it can then be garbage collected. You are only allowed to delete Nodes that don't have child Nodes; failing this, you must unlink the children from it or delete them first. After invoking this method you should let your external reference to the Node expire so the reminants are garbage collected.
delete_node_tree()
This "setter" method is like delete_node() except that it will also delete all of the invocant's primary descendant Nodes. Prior to deleting any Nodes, this method will first assert that every deletion candidate does not have any child (referencing) Nodes which live outside the tree being deleted. So this method will either succeed entirely or have no lasting effects. Note that this method, as well as delete_node(), is mainly intended for use by long-lived applications that continuously generate database commands at run-time and only use each one once, such as a naive interactive SQL shell, so to save on memory use; by contrast, many other kinds of applications have a limited and pre-determined set of database commands that they use, and they may not need this method at all.
get_container()
my $model = $node->get_container();This "getter" method returns the Container object which this Node lives in.
get_node_type()
my $type = $node->get_node_type();This "getter" method returns the Node Type scalar (enum) property of this Node. You can not change this property on an existing Node, but you can set it on a new one.
get_node_id()
This "getter" method will return the integral Node Id property of this Node.
set_node_id( NEW_ID )
This "setter" method will replace this Node's Id property with the new value given in NEW_ID if it can; the replacement will fail if some other Node with the same Node Id already exists in the same Container.
get_primary_parent_attribute()
my $parent = $node->get_primary_parent_attribute();This "getter" method returns the primary parent Node of the current Node, if there is one.
clear_primary_parent_attribute()
This "setter" method will clear this Node's primary parent attribute value, if it has one.
set_primary_parent_attribute( ATTR_VALUE )
This "setter" method will set or replace this Node's primary parent attribute value, if it has one, giving it the new value specified in ATTR_VALUE.
get_literal_attribute( ATTR_NAME )
This "getter" method will return the value for this Node's literal attribute named in the ATTR_NAME argument.
get_literal_attributes()
This "getter" method will fetch all of this Node's literal attributes, returning them in a Hash ref.
clear_literal_attribute( ATTR_NAME )
This "setter" method will clear this Node's literal attribute named in the ATTR_NAME argument.
clear_literal_attributes()
This "setter" method will clear all of this Node's literal attributes.
set_literal_attribute( ATTR_NAME, ATTR_VALUE )
This "setter" method will set or replace this Node's literal attribute named in the ATTR_NAME argument, giving it the new value specified in ATTR_VALUE.
set_literal_attributes( ATTRS )
This "setter" method will set or replace multiple Node literal attributes, whose names and values are specified by keys and values of the ATTRS hash ref argument; this method will invoke set_literal_attribute() for each key/value pair.
get_enumerated_attribute( ATTR_NAME )
This "getter" method will return the value for this Node's enumerated attribute named in the ATTR_NAME argument.
get_enumerated_attributes()
This "getter" method will fetch all of this Node's enumerated attributes, returning them in a Hash ref.
clear_enumerated_attribute( ATTR_NAME )
This "setter" method will clear this Node's enumerated attribute named in the ATTR_NAME argument.
clear_enumerated_attributes()
This "setter" method will clear all of this Node's enumerated attributes.
set_enumerated_attribute( ATTR_NAME, ATTR_VALUE )
This "setter" method will set or replace this Node's enumerated attribute named in the ATTR_NAME argument, giving it the new value specified in ATTR_VALUE.
set_enumerated_attributes( ATTRS )
This "setter" method will set or replace multiple Node enumerated attributes, whose names and values are specified by keys and values of the ATTRS hash ref argument; this method will invoke set_enumerated_attribute() for each key/value pair.
get_node_ref_attribute( ATTR_NAME[, GET_TARGET_SI] )
This "getter" method will return the value for this Node's node attribute named in the ATTR_NAME argument, if it is set, or undef if it isn't. The returned value is a Node ref by default; if the optional boolean argument GET_TARGET_SI is true, then this method will instead lookup (recursively) and return the target Node's literal or enumerated surrogate id value (a single value, not a chain).
get_node_ref_attributes([ GET_TARGET_SI ])
This "getter" method will fetch all of this Node's node attributes, returning them in a Hash ref. Each attribute value is returned in the format specified by get_node_ref_attribute( <attr-name>, GET_TARGET_SI ).
clear_node_ref_attribute( ATTR_NAME )
This "setter" method will clear this Node's node attribute named in the ATTR_NAME argument; the other Node being referred to will also have its child list reciprocal link to the current Node cleared.
clear_node_ref_attributes()
This "setter" method will clear all of this Node's node attributes; see the clear_node_ref_attribute() documentation for the semantics.
set_node_ref_attribute( ATTR_NAME, ATTR_VALUE )
This "setter" method will set or replace this Node's node attribute named in the ATTR_NAME argument, giving it the new value specified in ATTR_VALUE (if it is different). If the attribute was previously valued, this method will first invoke clear_node_ref_attribute() on it. When setting a new value it will also add the current Node to the other Node's child list. ATTR_VALUE may either be a perl reference to a Node, or a Node Id value, or a relative Surrogate Node Id value (scalar or array ref); the last one will only work if this Node is in a Container that matches Nodes by surrogate ids.
set_node_ref_attributes( ATTRS )
This "setter" method will set or replace multiple Node node attributes, whose names and values are specified by keys and values of the ATTRS hash ref argument; this method will invoke set_node_ref_attribute() for each key/value pair.
get_surrogate_id_attribute([ GET_TARGET_SI ])
This "getter" method will return the value for this Node's surrogate id attribute. The GET_TARGET_SI argument is relevant only for Node-ref attributes; its effects are explained by get_node_ref_attribute().
clear_surrogate_id_attribute()
This "setter" method will clear this Node's surrogate id attribute value, unless it is 'id', in which case it throws an exception instead.
set_surrogate_id_attribute( ATTR_VALUE )
This "setter" method will set or replace this Node's surrogate id attribute value, giving it the new value specified in ATTR_VALUE.
get_attribute( ATTR_NAME[, GET_TARGET_SI] )
my $curr_val = $node->get_attribute( 'si_name' );This "getter" method will return the value for this Node's attribute named in the ATTR_NAME argument. The GET_TARGET_SI argument is relevant only for Node-ref attributes; its effects are explained by get_node_ref_attribute().
get_attributes([ GET_TARGET_SI ])
my $rh_attrs = $node->get_attributes();This "getter" method will fetch all of this Node's attributes, returning them in a Hash ref. The GET_TARGET_SI argument is relevant only for Node-ref attributes; its effects are explained by get_node_ref_attribute().
clear_attribute( ATTR_NAME )
This "setter" method will clear this Node's attribute named in the ATTR_NAME argument, unless ATTR_NAME is 'id'; since the Node Id attribute has a constantly applied mandatory constraint, this method will throw an exception if you try.
clear_attributes()
This "setter" method will clear all of this Node's attributes, except 'id'.
set_attribute( ATTR_NAME, ATTR_VALUE )
This "setter" method will set or replace this Node's attribute named in the ATTR_NAME argument, giving it the new value specified in ATTR_VALUE.
set_attributes( ATTRS )
$node->set_attributes( $rh_attrs );This "setter" method will set or replace multiple Node attributes, whose names and values are specified by keys and values of the ATTRS hash ref argument; this method will invoke set_attribute() for each key/value pair.
move_before_sibling( SIBLING[, PARENT] )
This "setter" method allows you to change the order of child Nodes under a common parent Node; specifically, it moves the current Node to a position just above/before the sibling Node specified in the SIBLING Node ref argument, if it can. Since a Node can have multiple parent Nodes (and the sibling likewise), the optional PARENT argument lets you specify which parent's child list you want to move within; if you do not provide an PARENT value, then the current Node's primary parent Node (or pseudo-Node) is used, if possible. This method will throw an exception if the current Node and the specified sibling or parent Nodes are not appropriately related to each other (parent <-> child). If you want to move the current Node to follow the sibling instead, then invoke this method on the sibling.
get_child_nodes([ NODE_TYPE ])
my $ra_node_list = $table_node->get_child_nodes();
my $ra_node_list = $table_node->get_child_nodes( 'table_field' );This "getter" method returns a list of this Node's primary-child Nodes, in a new array ref. If the optional argument NODE_TYPE is defined, then only child Nodes of that Node Type are returned; otherwise, all child Nodes are returned. All Nodes are returned in the same order they were added.
add_child_node( CHILD )
$node->add_child_node( $child );This "setter" method allows you to add a new primary-child Node to this Node, which is provided as the single CHILD Node ref argument. The new child Node is appended to the list of existing child Nodes, and the current Node becomes the new or first primary parent Node of CHILD.
add_child_nodes( CHILDREN )
$model->add_child_nodes( [$child1,$child2] );This "setter" method takes an array ref in its single CHILDREN argument, and calls add_child_node() for each element found in it. This method does not return anything.
get_referencing_nodes([ NODE_TYPE ])
my $ra_node_list = $row_data_type_node->get_referencing_nodes();
my $ra_node_list = $row_data_type_node->get_referencing_nodes( 'table' );This "getter" method returns a list of this Node's link-child Nodes (which are other Nodes that refer to this one in a non-PP nref attribute) in a new array ref. If the optional argument NODE_TYPE is defined, then only child Nodes of that Node Type are returned; otherwise, all child Nodes are returned. All Nodes are returned in the same order they were added.
get_surrogate_id_chain()
This "getter" method returns the current Node's surrogate id chain as an array ref. This method's return value is conceptually like what get_relative_surrogate_id() returns except that it is defined in an absolute context rather than a relative context, making it less suitable for serializing models that are subsequently reorganized; it is also much longer.
find_node_by_surrogate_id( SELF_ATTR_NAME, TARGET_ATTR_VALUE )
my $table_node = $table_index_node->find_node_by_surrogate_id( 'f_table', 'person' );This "getter" method's first argument SELF_ATTR_NAME must match a valid Node-ref attribute name of the current Node (but not the 'pp' attribute); it throws an exception otherwise. This method searches for member Nodes of this Node's host Container whose type makes them legally linkable by the SELF_ATTR_NAME attribute and whose Surrogate Node Id matches the TARGET_ATTR_VALUE argument (which may be either a scalar or a Perl array ref); if one or more are found in the same scope then they are all returned by reference, within an array ref; if none are found, then undef is returned. The search is context sensitive and scoped; it starts by examining the Nodes that are closest to this Node's location in its Container's Node tree and then spreads outwards, looking within just the locations that are supposed to be visible to this Node. Variations on this search method come into play for Node types that are connected to the concepts of "wrapper attribute", "ancestor attribute correlation", and "remotely addressable types". Note that it is illegal to use the return value of get_surrogate_id_chain() as a TARGET_ATTR_VALUE with this method; you can give the return value of get_relative_surrogate_id(), however. Note that counting the number of return values from find_node_by_surrogate_id() is an accurate way to tell whether set_node_ref_attribute() with the same 2 arguments will succeed or not; it will only succeed if this method returns exactly 1 matching Node.
find_child_node_by_surrogate_id( TARGET_ATTR_VALUE )
my $table_index_node = $table_node->find_child_node_by_surrogate_id( 'fk_father' );This "getter" method searches for a primary-child Node of the current Node whose Surrogate Node Id matches the TARGET_ATTR_VALUE argument; if one is found then it is returned by reference; if none is found, then undef is returned. The TARGET_ATTR_VALUE argument is treated as an array-ref; if it is in fact not one, that single value is used as a single-element array. The search is multi-generational, one generation more childwards per array element; the first element matches a child of the invoked Node, the next element the child of the first matched child, and so on. If said array ref has undef as its first element, then this method behaves the same as Container.find_child_node_by_surrogate_id( TARGET_ATTR_VALUE ).
get_relative_surrogate_id( SELF_ATTR_NAME[, WANT_SHORTEST] )
my $longer_table_si_value = $table_index_node->get_relative_surrogate_id( 'f_table' );
my $shorter_table_si_value = $table_index_node->get_relative_surrogate_id( 'f_table', 1 );
my $longer_view_src_col_si_value = $view_expr_node->get_relative_surrogate_id( 'name' );
my $shorter_view_src_col_si_value = $view_expr_node->get_relative_surrogate_id( 'name', 1 );This "getter" method's first argument SELF_ATTR_NAME must match a valid Node-ref attribute name of the current Node (but not the 'pp' attribute); it throws an exception otherwise. This method returns a Surrogate Node Id value (which may be either a scalar or a Perl array ref) which is appropriate for passing to find_node_by_surrogate_id() as its TARGET_ATTR_VALUE such that the current attribute value would be "found" by it, assuming the current attribute value is valid; if none can be determined, then undef is returned. This method's return value is conceptually like what get_surrogate_id_chain() returns except that it is defined in a relative context rather than an absolute context, making it more suitable for serializing models that are subsequently reorganized; it is also much shorter. Depending on context circumstances, get_relative_surrogate_id() can possibly return either fully qualified (longest), partly qualified, or unqualified (shortest) Surrogate Id values for certain Node-ref attributes. By default, it will return the fully qualified Surrogate Id in every case, which is the fastest to determine and use, and which has the most resiliency against becoming an ambiguous reference when other parts of the SRT model are changed to have the same surrogate id attribute value as the target. If the optional boolean argument WANT_SHORTEST is set true, then this method will produce the most unqualified Surrogate Id possible that is fully unambiguous within the current state of the SRT model; this version can be more resilient against breaking when parts of the SRT model being moved around relative to each other, as long as there are no duplicate surrogate id attributes in the model, at the cost of being slower to determine and use. WANT_SHORTEST has no effect with the large fraction of Node refs whose fully qualified name is a single element.
assert_deferrable_constraints()
This "getter" method implements several types of deferrable data validation, to make sure that this Node is ready to be used; it throws an exception if it can find anything wrong.
CONTAINER OR NODE METHODS FOR DEBUGGING
The following 3 "getter" methods can be invoked either on Container or Node objects, and will return a tree-arranged structure having the contents of a Node and all its children (to the Nth generation). If you invoke the 3 methods on a Node, then that Node will be the root of the returned structure. If you invoke them on a Container, then a few pseudo-Nodes will be output with all the normal Nodes in the Container as their children.
get_all_properties([ LINKS_AS_SI[, WANT_SHORTEST] ])
$rh_node_properties = $container->get_all_properties();
$rh_node_properties = $container->get_all_properties( 1 );
$rh_node_properties = $container->get_all_properties( 1, 1 );
$rh_node_properties = $node->get_all_properties();
$rh_node_properties = $node->get_all_properties( 1 );
$rh_node_properties = $node->get_all_properties( 1, 1 );This method returns a deep copy of all of the properties of this object as non-blessed Perl data structures. These data structures are also arranged in a tree, but they do not have any circular references. Each node in the returned tree, which represents a single Node or pseudo-Node, consists of an array-ref having 3 elements: a scalar having the Node type, a hash-ref having the Node attributes, and an array-ref having the child nodes (one per array element). For each Node, all attributes are output, including 'id', except for the 'pp' attribute, which is redundant; the value of the 'pp' attribute can be determined from an output Node's context, as it is equal to the 'id' of the parent Node. The main purpose, currently, of get_all_properties() is to make it easier to debug or test this class; it makes it easier to see at a glance whether the other class methods are doing what you expect. The output of this method should also be easy to serialize or unserialize to strings of Perl code or xml or other things, should you want to compare your results easily by string compare; see "get_all_properties_as_perl_str()" and "get_all_properties_as_xml_str()". If the optional boolean argument LINKS_AS_SI is true, then each Node ref attribute will be output as the target Node's surrogate id value, as returned by get_relative_surrogate_id( <attr-name>, WANT_SHORTEST ), if it has a valued surrogate id attribute; if the argument is false, or a Node doesn't have a valued surrogate id attribute, then its Node id will be output by default. The output can alternately be passed as the CHILDREN parameter (when first wrapped in an array-ref) to build_container() so that the method creates a clone of the original Container, where applicable; iff the output was generated using LINKS_AS_SI, then build_container() will need to be given a true MATCH_SURR_IDS argument (its other boolean args can all be false).
get_all_properties_as_perl_str([ LINKS_AS_SI[, WANT_SHORTEST] ])
$perl_code_str = $container->get_all_properties_as_perl_str();
$perl_code_str = $container->get_all_properties_as_perl_str( 1 );
$perl_code_str = $container->get_all_properties_as_perl_str( 1, 1 );
$perl_code_str = $node->get_all_properties_as_perl_str();
$perl_code_str = $node->get_all_properties_as_perl_str( 1 );
$perl_code_str = $node->get_all_properties_as_perl_str( 1, 1 );This method is a wrapper for get_all_properties( LINKS_AS_SI ) that serializes its output into a pretty-printed string of Perl code, suitable for humans to read. You should be able to eval this string and produce the original structure.
get_all_properties_as_xml_str([ LINKS_AS_SI[, WANT_SHORTEST] ])
$xml_doc_str = $container->get_all_properties_as_xml_str();
$xml_doc_str = $container->get_all_properties_as_xml_str( 1 );
$xml_doc_str = $container->get_all_properties_as_xml_str( 1, 1 );
$xml_doc_str = $node->get_all_properties_as_xml_str();
$xml_doc_str = $node->get_all_properties_as_xml_str( 1 );
$xml_doc_str = $node->get_all_properties_as_xml_str( 1, 1 );This method is a wrapper for get_all_properties( LINKS_AS_SI ) that serializes its output into a pretty-printed string of XML, suitable for humans to read.
CONTAINER OR NODE FUNCTIONS AND METHODS FOR RAPID DEVELOPMENT
The following 6 "setter" functions and methods should assist more rapid development of code that uses SQL::Routine, at the cost that the code would run a bit slower (SQL::Routine has to search for info behind the scenes that it would otherwise get from you). These methods are implemented as wrappers over other SQL::Routine methods, and allow you to accomplish with one method call what otherwise requires about 4-10 method calls, meaning your code base is significantly smaller (unless you implement your own simplifying wrapper functions, which is recommended in some situations).
Note that when a subroutine is referred to as a "function", it is stateless and can be invoked off of either a class name or class object; when a subroutine is called a "method", it can only be invoked off of Container or Node objects.
build_node( NODE_TYPE[, ATTRS] )
my $nodeP = $model->build_node( 'catalog', { 'id' => 1, } );
my $nodeN = $node->build_node( 'catalog', { 'id' => 1, } ); This method will create and return a new Node, that lives in the invocant Container or in the same Container as the invocant Node, whose type is specified in NODE_TYPE, and also set its attributes. The ATTRS argument is mainly processed by Node.set_attributes() if it is provided; a Node id ('id') can also be provided this way, or it will be generated if that is allowed. ATTRS may also contain a 'pp' if applicable. If ATTRS is defined but not a Hash ref, then this method will build a new one having a single element, where the value is ATTRS and the key is either 'id' or the new Node's surrogate id attribute name, depending on whether the value looks like a valid Node id.
build_child_node( NODE_TYPE[, ATTRS] )
This method is like build_node() except that it will set the new Node's primary parent to be the Node that this method was invoked on, using add_child_node(); if this method was invoked on a Container, then it will work only for new Nodes that would have a pseudo-Node as their primary parent. When creating a Node with this method, you do not set any PP candidates in ATTRS (if a 'pp' attribute is given in ATTRS, it will be ignored).
build_child_nodes( CHILDREN )
This method takes an array ref in its single CHILDREN argument, and calls build_child_node() for each element found in it; each element of CHILDREN must be an array ref whose elements correspond to the arguments of build_child_node(). This method does not return anything.
build_child_node_tree( NODE_TYPE[, ATTRS][, CHILDREN] )
This method is like build_child_node() except that it will recursively create all of the child Nodes of the new Node as well; build_child_node_trees( CHILDREN ) will be invoked following the first Node's creation (if applicable). In the context of SQL::Routine, a "Node tree" or "tree" consists of one arbitrary Node and all of its "descendants". If invoked on a Container object, this method will recognize any pseudo-Node names given in 'NODE_TYPE' and simply move on to creating the child Nodes of that pseudo-Node, rather than throwing an error exception for an invalid Node type. Therefore, you can populate a whole Container with one call to this method. This method returns the root Node that it creates, if NODE_TYPE was a valid Node type; it returns the Container instead if NODE_TYPE is a pseudo-Node name.
build_child_node_trees( CHILDREN )
This method takes an array ref in its single CHILDREN argument, and calls build_child_node_tree() for each element found in it; each element of CHILDREN must be an array ref whose elements correspond to the arguments of build_child_node_tree(). This method does not return anything.
build_container([ CHILDREN[, AUTO_ASSERT[, AUTO_IDS[, MATCH_SURR_IDS]]] ])
When called with no arguments, this function is like new_container(), in that it will create and return a new Container object; if the array ref argument CHILDREN is set, then this function also behaves like build_child_node_trees( CHILDREN ) but that all of the newly built Nodes are held in the newly built Container. If any of the optional boolean arguments [AUTO_ASSERT, AUTO_IDS, MATCH_SURR_IDS] are true, then the corresponding flag properties of the new Container will be set to true prior to creating any Nodes. This function is almost the exact opposite of Container.get_all_properties(); you should be able to take the Array-ref output of Container.get_all_properties(), wrap that in another Array-ref (to produce a single-element list of Array-refs), give it to build_container(), and end up with a clone of the original Container.
INFORMATION FUNCTIONS AND METHODS
These "getter" functions/methods are all intended for use by programs that want to dynamically interface with SQL::Routine, especially those programs that will generate a user interface for manual editing of data stored in or accessed through SQL::Routine constructs. It will allow such programs to continue working without many changes while SQL::Routine itself continues to evolve. In a manner of speaking, these functions/methods let a caller program query as to what 'schema' or 'business logic' drive this class. These functions/methods are all deterministic and stateless; they can be used in any context and will always give the same answers from the same arguments, and no object properties are used. You can invoke them from any kind of object that SQL::Routine implements, or straight off of the class name itself, like a 'static' method. All of these functions return the undefined value if they match nothing.
valid_enumerated_types([ ENUM_TYPE ])
This function by default returns a list of the valid enumerated types that SQL::Routine recognizes; if the optional ENUM_TYPE argument is given, it just returns true if that matches a valid type, and false otherwise.
valid_enumerated_type_values( ENUM_TYPE[, ENUM_VALUE] )
This function by default returns a list of the values that SQL::Routine recognizes for the enumerated type given in the ENUM_TYPE argument; if the optional ENUM_VALUE argument is given, it just returns true if that matches an allowed value, and false otherwise.
valid_node_types([ NODE_TYPE ])
This function by default returns a list of the valid Node Types that SQL::Routine recognizes; if the optional NODE_TYPE argument is given, it just returns true if that matches a valid type, and false otherwise.
node_types_with_pseudonode_parents([ NODE_TYPE ])
This function by default returns a Hash ref where the keys are the names of the Node Types whose primary parents can only be pseudo-Nodes, and where the values name the pseudo-Nodes they are the children of; if the optional NODE_TYPE argument is given, it just returns the pseudo-Node for that Node Type.
node_types_with_primary_parent_attributes([ NODE_TYPE ])
This function by default returns a Hash ref where the keys are the names of the Node Types that have a primary parent ("pp") attribute, and where the values are the Node Types that values for that attribute must be; if the optional NODE_TYPE argument is given, it just returns the valid Node Types for the primary parent attribute of that Node Type. Since there may be multiple valid primary parent Node Types for the same Node Type, an array ref is returned that enumerates the valid types; often there is just one element; if the array ref has no elements, then all Node Types are valid.
valid_node_type_literal_attributes( NODE_TYPE[, ATTR_NAME] )
This function by default returns a Hash ref where the keys are the names of the literal attributes that SQL::Routine recognizes for the Node Type given in the NODE_TYPE argument, and where the values are the literal data types that values for those attributes must be; if the optional ATTR_NAME argument is given, it just returns the literal data type for the named attribute.
valid_node_type_enumerated_attributes( NODE_TYPE[, ATTR_NAME] )
This function by default returns a Hash ref where the keys are the names of the enumerated attributes that SQL::Routine recognizes for the Node Type given in the NODE_TYPE argument, and where the values are the enumerated data types that values for those attributes must be; if the optional ATTR_NAME argument is given, it just returns the enumerated data type for the named attribute.
valid_node_type_node_ref_attributes( NODE_TYPE[, ATTR_NAME] )
This function by default returns a Hash ref where the keys are the names of the node attributes that SQL::Routine recognizes for the Node Type given in the NODE_TYPE argument, and where the values are the Node Types that values for those attributes must be; if the optional ATTR_NAME argument is given, it just returns the Node Type for the named attribute. Since there may be multiple valid Node Types for the same attribute, an array ref is returned that enumerates the valid types; often there is just one element; if the array ref has no elements, then all Node Types are valid.
valid_node_type_surrogate_id_attributes([ NODE_TYPE ])
This function by default returns a Hash ref where the keys are the names of the Node Types that have a surrogate id attribute, and where the values are the names of that attribute; if the optional NODE_TYPE argument is given, it just returns the surrogate id attribute for that Node Type. Note that a few Node types don't have distinct surrogate id attributes; for those, this method will return 'id' as the surrogate id attribute name.
OLDER DOCUMENTATION
These sections were written during the earlier days of SQL::Routine when there was an intention to make a C version of it some time in the future. While that may still happen, it is more likely that a Parrot-hosted solution will be used instead. In any event, what follows is mostly pristine from year one, originally stored in its own file named API_C.pod, before being moved here; some details shouldn't be considered accurate.
A SECOND VERSION IN C
The first releases of SQL::Routine are being implemented in pure Perl 5 thanks mainly to the heritage of original intention for using it with Perl programs, and otherwise to the fact that Perl is great for rapid prototyping, and has a large existing support for talking to databases, via the mature DBI framework, upon which to build. One longer term goal, however, is that SQL::Routine will be a pure ANSI C library which has optional bindings for multiple other languages, such as C++, Objective-C, Perl 5 (most importantly), Parrot and Perl 6, Python, PHP 4+, Java, and whatever else users want.
This has practical benefits such as compatability with databases for which there is no existing Perl support (all database drivers already have C support), and the ability to use it with any favorite programming language (which can bring in developers from those communities aka Parrot). Moreover, and most easily guessed, C is a lot more efficient in both CPU and memory considering the huge amount of data processing that SQL::Routine has to do. There are good reasons for things like LIBXML, GD, and DBI to be written in C which are applicable to SQL::Routine also. To that end, SQL::Routine is being designed from the ground up to be easily implemented in either Perl 5 or C, in both cases using an object-oriented conceptual process.
This document is a reference for a SQL::Routine C API that is being planned, consisting mainly of the C header files (struct definitions and function declarations) that the actual SQL::Routine core will end up being. After all, SQL::Routine is actually more of an interface or protocol definition than an actual implementation (although it includes those parts too). This is intended to give programmers an idea why the design is going the way that it is and why details that pure Perl programs don't necessarily have to know about are being considered. While pure C is not object oriented at all, the SQL::Routine API is designed to be as object-like as possible, such that each C struct for storing data will have a corresponding set of functions for interfacing with it, and the details for memory allocation and deallocation are handled by those also.
Note that the core libraries are intended to not have any external dependencies, except for data type handling libraries such as for string or sparse list handling. These classes do not do any I/O and they do not talk to the operating system, so they should be fully portable. All such things are relegated to extensions like the Engines.
Note also that the following should be considered almost-C rather than perfect C. The reasoning is that my experience in writing C is rusty at the moment and I haven't necessarily tried to compile these yet. For the moment they are just a type of documentation. They will be improved.
AN ALTERNATIVE SECOND VERSION
Inspired by the recent (February 2004) formation of dbdi-dev@perl.org, a group which aims to make a Parrot-native database access framework for all Parrot hosted languages, and that can talk to native database drivers through Parrot's Native Call Interface, meaning that the Parrot database project doesn't need any parts written in C, I may decide to take the same approach with the next major version of SQL::Routine and related projects, implementing it in IMC instead of C.
More recently (March 2005), considering that a working Perl 6 engine is already taking shape separately from Parrot (see Autrijus Tang's "Pugs" distribution), I will probably just make the second version in Perl 6 instead. If an IMC version is made, it will be done later for the sake of better performance.
CONTENT OF libSQLRT.h
#ifndef _libSQLRT_h
#define _libSQLRT_h
/************************************************************************/
/* define some simple data types here */
typedef unsigned char sqlrt_dt_flag; /* stores only two values: 0 (false) or 1 (true) */
typedef unsigned char sqlrt_dt_octet; /* a generic eight-bit value */
typedef unsigned int sqlrt_dt_scale; /* a precise integer between 0 and +4,294,967,295 */
typedef struct {
sqlrt_dt_octet* string_data; /* not null terminated */
sqlrt_dt_scale used_octets;
sqlrt_dt_scale buff_octets;
} sqlrt_dt_label; /* an arbitrary sized UTF-8 character string, up to 4 gigabytes */
typedef enum {
SQLRT_LITP_NUM_INT , /* an exact integral or whole number/numeric */
SQLRT_LITP_NUM_EXA , /* an exact decimal or fractional number/numeric */
SQLRT_LITP_NUM_APR , /* an approximately represented number/numeric (eg: floating point) */
SQLRT_LITP_STR_BIT , /* a string of bits or generic binary data (can store anything) */
SQLRT_LITP_STR_CHAR , /* a string of characters (encoding spec defined separately) */
SQLRT_LITP_BOOLEAN , /* only two values: false or true */
SQLRT_LITP_DATM_FULL, /* a full datetime ('timestamp') having both YMD and HMS components */
SQLRT_LITP_DATM_DATE, /* a valid Gregorian (says the 2003,1999 standard) date having just YMD */
SQLRT_LITP_DATM_TIME, /* a valid time of day having just HMS components */
SQLRT_LITP_INTRVL_YM, /* a time duration having year-month (YM) intervals (year or month or both) */
SQLRT_LITP_INTRVL_DT /* a time duration having day-time (DHMS) intervals (but not year or month) */
} sqlrt_dt_literal_type;
typedef enum {
SQLRT_CHENTP_UTF8 , /* unicode UTF-8 (always byte-order preserving; no big/little endian, usually 1 octet) */
SQLRT_CHENTP_UTF16 , /* unicode UTF-16 (has big/little endian versions) */
SQLRT_CHENTP_UTF32 , /* unicode UTF-32 (has big/little endian versions) */
SQLRT_CHENTP_ASCII , /* 8-bit ascii */
SQLRT_CHENTP_EBSDIC /* 8-bit ebsdic */
/* others will be added as appropriate */
} sqlrt_dt_char_enc_type;
typedef struct {
sqlrt_dt_literal_type literal_type ; /* says how to interpret other struct properties */
sqlrt_dt_scale fixed_octets ; /* when literal is NUM_INT, NUM_APR; usu 1,2,4,8 */
sqlrt_dt_char_enc_type char_enc_type; /* when literal is a STR_CHAR, how it is encoded */
sqlrt_dt_octet* literal_data ; /* not null terminated (or null part of trail junk) */
/* above never ref'd by mult structs; struct itself can be ref'd by multiple vars */
sqlrt_dt_scale used_octets ; /* doesn't include any trailing null with strings */
sqlrt_dt_scale buff_octets ; /* does include or surpass any trailing null */
/* other metadata may be added as appropriate; we may embed some fixed width type data */
sqlrt_dt_scale malcvar_refs ; /* count of refs to this struct from malloc'd vars */
} sqlrt_dt_literal;
/************************************************************************/
/* define some simple data types here */
typedef enum {
SQLRT_ENST_FOO, /* replace with semi-long actual list of generic enumerated value sets */
SQLRT_ENST_BAR
} sqlrt_dt_enum_set;
typedef enum {
SQLRT_ENIT_FOO, /* replace with long actual list of generic enumerated value set members */
SQLRT_ENIT_BAR /* this enum may need repl w const list or ml en union, if sev key can't have same int */
} sqlrt_dt_enum_item;
typedef enum {
SQLRT_NDTP_FOO, /* replace with semi-short actual list of Node Types */
SQLRT_NDTP_BAR
} sqlrt_dt_node_type;
typedef enum {
SQLRT_NDATNM_FOO, /* replace with actual list of Node Attribute Names */
SQLRT_NDATNM_BAR /* this enum may need repl w const list or ml en union, if sev key can't have same int */
} sqlrt_dt_node_atnm;
typedef struct {
sqlrt_dt_node_type node_type ; /* what type of Node this is */
sqlrt_dt_scale node_id ; /* uniq ident for Node within Container+Type */
sqlrt_dt_node* pp_nref ; /* (ref) primary-parent ('pp') Node attr */
sqlrt_dt_literal* at_literals ; /* (array) attrs of Node which are literals */
sqlrt_dt_enum_item* at_enums ; /* (array) attrs of Node which are enumerated values */
sqlrt_dt_node* at_nrefs ; /* (array of ref) attrs of Node which are Nodes */
/* Note: if it would be better, we may combine all at* into one longer union list */
sqlrt_dt_container* container ; /* (ref) what Container this Node lives in, if any */
sqlrt_dt_node_dll* prim_child_nrefs; /* (list of refs) recipr to Nodes whose pp_nref ref to us */
sqlrt_dt_node_dll* link_child_nrefs; /* (list of refs) recipr to Nodes whose at_nodes ref to us */
} sqlrt_dt_node;
typedef struct {
sqlrt_dt_node* item; /* the actual Node represented by this list item */
sqlrt_dt_node_dll* next; /* next Node in list, if any */
sqlrt_dt_node_dll* prev; /* previous Node in list, if any */
} sqlrt_dt_node_dll; /* doubly-linked-list; use when number of list items not known in advance */
typedef struct {
sqlrt_dt_node_dll* all_nodes; /* (list of refs) all Nodes in this Container */
} sqlrt_dt_container;
/************************************************************************/
/* define some accessor functions here */
/************************************************************************/
#endif /* _libSQLRT_h */SEE ALSO
SQL::Routine and the various other modules mentioned in its SEE ALSO.