1DBIx::Class::Storage::DUBsIe:r:OCDoBnCt:r:iAbCuCtEeDSdBSI(Px3e:)r:lClDaoscsu:m:eSnttoartaigoen::DBI::ODBC::ACCESS(3)
2
3
4
6 DBIx::Class::Storage::DBI::ODBC::ACCESS - Support specific to MS Access
7 over ODBC
8
10 I am not a DBI, DBIx::Class or MS Access guru. Use this module with
11 that in mind.
12
13 This module is currently considered alpha software and can change
14 without notice.
15
17 This class implements support specific to Microsoft Access over ODBC.
18
19 It is loaded automatically by by DBIx::Class::Storage::DBI::ODBC when
20 it detects a MS Access back-end.
21
23 This module have currently only been tested on MS Access 2003 using the
24 Jet 4.0 engine.
25
26 As far as my knowledge it should work on MS Access 2000 or later, but
27 that have not been tested. Information about support for different
28 version of MS Access is welcome.
29
31 MS Access supports the @@IDENTITY function for retrieving the id of the
32 latest inserted row. @@IDENTITY is global to the connection, so to
33 support the possibility of getting the last inserted id for different
34 tables, the insert() function stores the inserted id on a per table
35 basis. last_insert_id() then just returns the stored value.
36
38 Invalid precision value
39 This error message is received when trying to store more than 255
40 characters in a MEMO field. The problem is (to my knowledge) an
41 error in the MS Access ODBC driver. The problem is fixed by setting
42 the "data_type" of the column to "SQL_LONGVARCHAR" in
43 "add_columns". "SQL_LONGVARCHAR" is a constant in the "DBI"
44 module.
45
47 bind_attribute_by_data_type
48 This function currently supports the SQL_LONGVARCHAR column type.
49
50 insert
51 last_insert_id
52 sqlt_type
54 Most likely. Bug reports are welcome.
55
57 A~Xystein Torget "<oystein.torget@dnv.com>"
58
60 You may distribute this code under the same terms as Perl itself.
61
62 Det Norske Veritas AS (DNV)
63
64 http://www.dnv.com
65
66
67
68perl v5.12.0 201D0B-I0x5:-:1C2lass::Storage::DBI::ODBC::ACCESS(3)