A year ago, I was only trying to “rescue” Andromeda …
When I started the Pyrseas project, I was mainly interested in improving on the basic table/column version control of Andromeda. I never thought I’d be adding support for “exotic” features such as base types, operators or operator classes. However, the initial feedback led me to set my sights much higher: Pyrseas was to offer support for all PostgreSQL data definition features.
Over the past two and a half months, I’ve added coverage for those advanced features and more. I’m glad to report that, with the help of Leo Hsu and Regina Obe, the Pyrseas tools are now able to output all the objects1 in a database loaded with postgis.sql, spatial_ref_sys.sql and postgis_comments.sql from PostGIS 1.5, in YAML format. The tools are also able to take in that YAML and generate the SQL necessary to recreate all those objects, in the correct order, on an empty database, as well as to reverse the process.
|FOREIGN DATA WRAPPER|
|– CHECK CONSTRAINT||X||X||X||X|
|– PRIMARY KEY||X||X||X||X|
|– FOREIGN KEY||X||X||X||X|
|– UNIQUE CONSTRAINT||X||X||X||X|
|TEXT SEARCH CONFIGURATION|
|TEXT SEARCH DICTIONARY|
|TEXT SEARCH PARSER|
|TEXT SEARCH TEMPLATE|
|– base type||X|
I’d like to thank Leo and Regina for their help, as well aquilax, mhow and acornett at GitHub for being early adopters and raising issues to improve Pyrseas functionality.
If you have a challenging PostgreSQL database, I’d like to encourage you to give Pyrseas a try, and let me know how it works out.
1 For those interested, this includes 2 tables, 1 view, 9 base types, 1 composite type, 777 functions, 17 aggregate functions, 19 casts, 4 operator classes/families, 23 operators, and 315 comments.