115 Commits (0b7026d964c79515c8df00b37ab41d550bcdcbde)

Author	SHA1	Message	Date
Bruce Momjian	1d8bbfd2e7	Make functions static where possible, enclose unused functions in #ifdef NOT_USED.	29 years ago
Bruce Momjian	ea5b5357cd	Remove more (void) and fix -Wall warnings.	29 years ago
Thomas G. Lockhart	215bc83d75	Remove #ifdef'd support for old i/o styles. ... Change box terminology from "length" to "width". Use length terminology in common with other geometric types (usually perimeter). Fix bugs in line arithmetic which resulted in bad intersection calculations. Deprecate temporary unstored slope fields. Check explicitly for intersections at endpoints to avoid rounding ugliness. Add center() routines for lseg, path, polygon. Add distance() routines for circle-polygon, polygon-polygon. Check explicitly for points and polygons contained within polygons using an axis-crossing algorithm. (Old code just checked bounding boxes). Add routine to convert circle-box. *whew*	29 years ago
Thomas G. Lockhart	06ea3c9a24	Add upgradepath(), isoldpath(), upgradepoly() and revertpoly() to allow ... migration from pre-v6.1 geometric data types. Only allow new input syntax for paths and polygons.	29 years ago
Bruce Momjian	afb089d4a4	Put back old lines.	29 years ago
Bruce Momjian	93b03649d4	Cleanup for AIX from Darren.	29 years ago
Thomas G. Lockhart	ac534bee01	Clean up redundant tests for valid pointers in geometric types. ... Fix up decoder field masks for timespan and reltime.	29 years ago
Marc G. Fournier	3e871388b5	From: Darren King <aixssd!darrenk@abs.net> ... Subject: [PATCHES] Re: [PORTS] AIX 6.1 fixes... Here are the patches for the two things that wouldn't make it thru the AIX compiler. The geo_ops.c change is harmless I believe. The nbtcompare.c patch fixes me, but I don't know about any other ports. Maybe wait on that one until Vadim decides what to do about the unsigned vs signed chars varlena issue.	29 years ago
Marc G. Fournier	6ea80b470b	From: Olaf Mittelstaedt <MSTAEDT@va-sigi.va.fh-ulm.de> ... Minor patches to geo_ops.c to clean up compile under AIX 4.1.3	29 years ago
Thomas G. Lockhart	64d9b50893	Fix timezone manipulation code to avoid crashes on some machines. ... Add type conversion functions for floating point numbers. Check for zero in unary minus floating point code (IEEE allows an explicit negative zero which looks ugly in a query result!). Ensure circle type has non-negative radius.	29 years ago
Thomas G. Lockhart	d464e31593	Remove valid pointer checks for returns from palloc() since palloc() will not ... return if storage is not allocated. Ref: Vadim 97/05/01	29 years ago
Marc G. Fournier	094ec2d3f3	More timezone patches by Thomas: ... Here are patches which should help fix timezone problems in the datetime and abstime code. Also, I repatched varlena.c to add in some comments and a little error checking on top of Vadim's earlier repairs. There are slight mods to the circle data type to have the distance operator between circles measure the distance between closest points rather than between centers.	29 years ago
Marc G. Fournier	9e2a87b62d	Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov> ... OK, here are a passel of patches for the geometric data types. These add a "circle" data type, new operators and functions for the existing data types, and change the default formats for some of the existing types to make them consistant with each other. Current formatting conventions (e.g. compatible with v6.0 to allow dump/reload) are supported, but the new conventions should be an improvement and we can eventually drop the old conventions entirely. For example, there are two kinds of paths (connected line segments), open and closed, and the old format was '(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4) '(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4) Pretty arcane, huh? The new format for paths is '((1,2),(3,4))' for a closed path with two points (1,2) and (3,4) '[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4) For polygons, the old convention is '(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3) and the new convention is '((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3) Other data types which are also represented as lists of points (e.g. boxes, line segments, and polygons) have similar representations (they surround each point with parens). For v6.1, any format which can be interpreted as the old style format is decoded as such; we can remove that backwards compatibility but ugly convention for v7.0. This will allow dump/reloads from v6.0. These include some updates to the regression test files to change the test for creating a data type from "circle" to "widget" to keep the test from trashing the new builtin circle type.	29 years ago
Marc G. Fournier	53d8be3bbf	Date/Time updates from Thomas...	29 years ago
Bruce Momjian	b913dd1f9e	Add prototypes for oracle-compat functions. Rename geo-*.c adt to geo_*.c	29 years ago
Marc G. Fournier	c9002ecb21	Produce a clean compile of backend...	30 years ago
Marc G. Fournier	18a7989e1a	- merging in Dr. George's tree with ours ... - src/backend/access - no changes - src/backend/utils - mostly cosmetic changes - ESCAPE_PATCH Added - src/Makefile.global changes merged	30 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago