- SUPPORTED VERSIONS
- IMPLEMENTATION NOTES
- KNOWN ACCESS PROBLEMS
- IMPLEMENTED FUNCTIONS
DBIx::Class::Storage::DBI::ODBC::ACCESS - Support specific to MS Access over ODBC
I am not a DBI, DBIx::Class or MS Access guru. Use this module with that in mind.
This module is currently considered alpha software and can change without notice.
This class implements support specific to Microsoft Access over ODBC.
It is loaded automatically by by DBIx::Class::Storage::DBI::ODBC when it detects a MS Access back-end.
This module have currently only been tested on MS Access 2003 using the Jet 4.0 engine.
As far as my knowledge it should work on MS Access 2000 or later, but that have not been tested. Information about support for different version of MS Access is welcome.
MS Access supports the @@IDENTITY function for retrieving the id of the latest inserted row. @@IDENTITY is global to the connection, so to support the possibility of getting the last inserted id for different tables, the insert() function stores the inserted id on a per table basis. last_insert_id() then just returns the stored value.
KNOWN ACCESS PROBLEMS
- Invalid precision value
This error message is received when trying to store more than 255 characters in a MEMO field. The problem is (to my knowledge) an error in the MS Access ODBC driver. The problem is fixed by setting the
data_typeof the column to
SQL_LONGVARCHARis a constant in the
This function currently supports the SQL_LONGVARCHAR column type.
Most likely. Bug reports are welcome.
You may distribute this code under the same terms as Perl itself.
Det Norske Veritas AS (DNV)
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 120:
Non-ASCII character seen before =encoding in 'Øystein'. Assuming ISO8859-1