1DBIx::Class::Storage::DUBsIe:r:ACDoOn:t:rMiSb_uJteetdD(B3PI)exr:l:CDloacsusm:e:nSttaotriaogne::DBI::ADO::MS_Jet(3)
2
3
4
6 DBIx::Class::Storage::DBI::ADO::MS_Jet - Support for MS Access over ADO
7
9 This driver is a subclass of DBIx::Class::Storage::DBI::ADO and
10 DBIx::Class::Storage::DBI::ACCESS for connecting to MS Access via
11 DBD::ADO.
12
13 See the documentation for DBIx::Class::Storage::DBI::ACCESS for
14 information on the MS Access driver for DBIx::Class.
15
16 This driver implements workarounds for "TEXT/IMAGE/MEMO" columns, sets
17 the cursor_class to DBIx::Class::Storage::DBI::ADO::MS_Jet::Cursor to
18 normalize returned "GUID" values and provides
19 DBIx::Class::InflateColumn::DateTime support for "DATETIME" columns.
20
22 # older Access versions:
23 dbi:ADO:Microsoft.Jet.OLEDB.4.0;Data Source=C:\Users\rkitover\Documents\access_sample.accdb
24
25 # newer Access versions:
26 dbi:ADO:Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\rkitover\Documents\access_sample.accdb;Persist Security Info=False'
27
29 The ADO driver does not suffer from the problems the ODBC driver has
30 with these types of columns. You can use them safely.
31
32 When you execute a "CREATE TABLE" statement over this driver with a
33 "TEXT" column, it will be converted to "MEMO", while in the ODBC driver
34 it is converted to "VARCHAR(255)".
35
36 However, the caveat about LongReadLen having to be twice the max size
37 of your largest "MEMO/TEXT" column +1 still applies. DBD::ADO sets
38 LongReadLen to a large value by default, so it should be safe to just
39 leave it unset. If you do pass a LongReadLen in your connect_info, it
40 will be multiplied by two and 1 added, just as for the ODBC driver.
41
43 Check the list of additional DBIC resources.
44
46 This module is free software copyright by the DBIx::Class (DBIC)
47 authors. You can redistribute it and/or modify it under the same terms
48 as the DBIx::Class library.
49
50
51
52perl v5.32.0 2020D-B0I7x-:2:8Class::Storage::DBI::ADO::MS_Jet(3)