Changes for version v0.9.15 - 2021-08-20
- Moved on_conflict from DB::Object to DB::Object::Tables, and DB::Object::Postgres to DB::Object::Postgres::Table and DB::Object::SQLite to DB::Object::SQLite::Tables where it belongs
- Moved alias as_string avoid insert limit local order replace reset returning reverse select sort tie unix_timestamp update where to L<DB::Object::Query>
- Updated the pod documentation with links for all of the above
- Corrected a small bug in DB::Object::Postgres::Tables->on_conflict whereby an error was assumed when the turn value from DB::Object::Postgres::Query->on_conflict was false, but the latter returned a legitimate empty string that was mis-construed as an error
- In DB::Object->table, which is used to instantiate DB::Object::Tables object, since it uses a cache to increase speed, here if a cached table object, it is cloned before it is returned to avoid undesirable effect like some table alias previously set and disturbing potential new queries.
- Added some typical typo-catching warnings in where clause in DB::Object::Query->_where_having when a field object (DB::Object::Fields::Field) is provided without assignment.
- Added coding typo catching in DB::Object::Tables::AUTOLOAD for when the user called a table field on a table object instead of using the table fields object method 'fields_object'
- Corrected bug where chained method like select->join lead to loss of properties which disrupted the join condition
Documentation
SQL Query Clause Object
Modules
SQL API
Table Cache
Tables Fields Object Accessor
Table Field Object
Mysql Database Object
Query Object for MySQL
Statement Object for MySQL
MySQL Table Object
SQL API
Large Object
Query Object for PostgreSQL
PostgreSQL Statement Object
PostgreSQL Table Object
Query Object
DB Object SQLite Driver
SQLite Query Object
SQLite Statement Object
SQLite Table Object
Statement Object
Database Table Object
Provides
in lib/DB/Object.pm
in lib/DB/Object.pm
in lib/DB/Object.pm
in lib/DB/Object.pm
in lib/DB/Object/Query.pm