On Thu, 11 Aug 2011 21:53:36 +0200, "Steffen Winkler"
wrote:
> Thank you, but there is mistake in trunk/DBI.pm
>
>,--- should be a "m"
> v
> 330: po_ => { class => 'DBD::MO', },
> 342: po_ => { class => 'DBD::PO', },
Oh my! yank-put fail
Is it necessary for each DBI driver to have a prefix registered in DBI itself,
or is this only necessary when the driver wishes to expose extra public methods?
If the DBD doesn't expose custom methods, can it be used without the prefix
registration? -- Darren Duncan
Thank you, but there is mistake in trunk/DBI.pm
,--- should be a "m"
v
330: po_ => { class => 'DBD::MO', },
342: po_ => { class => 'DBD::PO', },
The change report in "Changes" is ok.
--Steffen
Original-Nachricht
> Datum:
On Thu, 11 Aug 2011 07:28:00 +0200, "Steffen Winkler"
wrote:
> Hallo together,
>
> that is a good idea to register a prefix.
> To ask is better than me during creating DBD::PO and the picked 'po_'.
> I apologize for.
>
> I ask now for register 'mo_' for DBD::MO.
> That is my plan with some work