Re: [PDO] Mapping data type/size

[email protected] (Lester Caine) Thu, 29 Oct 2009 07:48:45 +0000
Newsgroups php.pdo
Message-ID <[email protected]>
Lukas

I think this is the key point I was asking about ...

>> The bottom line is that we have to know the 
>> structure of the table before we can use it? We can't simply ask for 
>> those details from the database and adjust things accordingly?

ADOdb returns the metadata for a table or query, and then the drivers 
can modify operation to provide a compatible result across all sources. 
This is the area that PDO does not currently support - if I'm reading 
the information correctly? There is an experimental meta data call on 
the result, but not for the prepared query or for tables in the database?

It also looks like the reason that the PDO driver 'in' ADOdb is unable 
to actually do some of the automatic data matching magic :(

In theory I should just be able to switch between Firebird and 
PDO:Firebird in ADOdb and compare results, but at present much of the 
information needed is not available from PDO. One has to manually feed 
in the fact that a field is a character string rather than a blob, but 
even that can't actually be handled in PDO currently?

I'm not trying to be difficult, but I can't currently see how to make 
PDO work for me with Firebird which is why I can't even get to the 
debugging stage. Until I can get it to transparently handle the data 
problems I can't even start looking at other aspects. And it's not just 
Firebird, Oracle has the same problem with CLOB ...

The real question here is WHAT is the base that PDO is working on 
currently? Having been through the steps of hand converting a MySQL 
database schema into one that will work with Firebird in order to test 
PDO - ignoring the SQL problems - one finds that the 'normal' mappings 
that I've been using ( and describing in conference papers over the last 
5 years ) simply do not work with PDO. Yes I can ignore BLOB fields and 
map to something that works, but in CMS systems, that considerably 
restricts the size of the content. So do I need to restructure the 
pdo_firebird driver so that it does not use streams by default just to 
get to a state where things can move forward?

To me there seems a lot of work still needs to be done, and I have 
systems working perfectly without PDO ... transparent across many databases.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php