GitLab

we have too many reg starting variables to use shortened names

replaced reg with registry for more explicit code

if we use first_registry and last_registry throughout the module, we can probably afford to use registry rather than reg for the simpler cases

helps for consistency across modules
also makes it easier to grep for registry calls, reg is too generic (regulatory, region, registry...)

seq_regon_name would never have worked, so the warn would have ended up as a fail

Simple formatting changes suggested by Bron. Will make the example cut-paste
usable.

Patch submitted by Leo for PGSQL default port number.

We have decided to revert this change. GeneBuilder code has a link to the
existing functionality manifesting itself as subtle silent breakages. The
old functionality has been brought back. Warning added about how possibly
bad using the array from this function is.

if your meta_coord table is wrong, you should run update_meta_coord.pl, not meta_levels.pl

After talking to Compara we found the need to support additional
lookups with the full id cache. Since all values are stored in memory
the lookup is very easy to compute.

Leo submitted patch. We support pgsql as a way of defining the driver. This
is inline with us accepting sqlite as a valid synonym for DBD::SQLite.

To provide improved querying of caches we now support SQL statements. These
queries return a list of keys (normally primary key db identifiers) defining
a list of objects to return. It is up to sub-BaseCache implementations to
deal with the nitty gritty of cache mis-hits (something they need to do
anyway).

- seq: pass defined slice intervals to trigger the correct program flow in SequenceAdaptor
- project: removed since believed to have bugs
- project_org: removed since it's not used anywhere

The code previously allowed bogus numbers through into the final slice which
caused errors in later methods. The website crashed because of this. We will
reject anything that was not an integer if the start or end was defined.

Nathan requested methods which can perform this kind of task (assert the contents
of a data structure). We support 1 level of arrays and hashes. All test cases
pass at time of writing. Methods for capturing method returns were
not implemented. They do not fit into the Utils way of doing (no method
actually performs a task on an object they just report what it is).

Removed get_all_ExternalFeatures method, now borrowed from parent where the corresponding adaptor handle the circular slice case

Removed some Slice overridden get_all_(Feature) methods since features/slices spanning the origin of replication are handled the corresponding feature adaptor

Check feature out of destination slice. SimpleFeatureAdaptor debugged in the negative strand slice case

Removed methods get_all_(Genes|Transcripts|Exons|Attributes) which weren't doing the correct thing in case of slices and features spanning the origin of replication