The Open Geospatial Consortium (OGC) is an international consortium of more than 250 companies, agencies, and universities participating in the development of publicly available conceptual solutions that can be useful with all kinds of applications that manage spatial data.The Open Geospatial Consortium publishes the , a document that proposes several conceptual ways for extending an SQL RDBMS to support spatial data.The specification describes a set of SQL geometry types, as well as functions on those types to create and analyze geometry values.
I do have a question though: I have a table (called tbl_globals) where I store several site-wide variables (which are echoed throughout the site and on more than one occasion).
They are variables such as org's phone number, site's name, etc.
This particular table only has one row (and no additional rows are ever added) In the past I have queried the table in the database and assigned a variable to each resulting value, which is fine.
This term refers to an SQL environment that has been extended with a set of geometry types.
A geometry-valued SQL column is implemented as a column that has a geometry type.
you can collect or ignoreaffected_rows// returns the number of rows in a table affected by your query// can be used after UPDATE query (to see how many rows are updated)// can be used after SELECT query (to see how many rows will be returned)Since it's a singleton, when you "create" your second $db_2 it's just reusing the first object, not opening/creating a new connection.