Re: thorny problem with table_info implementation

2013-09-03 Thread Tim Bunce
On Mon, Sep 02, 2013 at 08:53:18PM +0100, Martin J. Evans wrote: On 02/09/2013 20:27, Martin J. Evans wrote: Now, table_info() with no arguments is not mentioned in the DBI pod so you could say that is undefined behaviour but it is a little late for that now as DBD::ODBC uses it in test code

Re: thorny problem with table_info implementation

2013-09-03 Thread Martin J. Evans
On 03/09/13 09:38, Tim Bunce wrote: On Mon, Sep 02, 2013 at 08:53:18PM +0100, Martin J. Evans wrote: On 02/09/2013 20:27, Martin J. Evans wrote: Now, table_info() with no arguments is not mentioned in the DBI pod so you could say that is undefined behaviour but it is a little late for that

Re: thorny problem with table_info implementation

2013-09-03 Thread Martin J. Evans
On 03/09/2013 11:43, Martin J. Evans wrote: On 03/09/13 09:38, Tim Bunce wrote: On Mon, Sep 02, 2013 at 08:53:18PM +0100, Martin J. Evans wrote: On 02/09/2013 20:27, Martin J. Evans wrote: Now, table_info() with no arguments is not mentioned in the DBI pod so you could say that is undefined

Re: thorny problem with table_info implementation

2013-09-02 Thread Martin J. Evans
On 02/09/2013 20:27, Martin J. Evans wrote: Hi, Firstly, I've just come back from holidays, I'm distracted by other things right now and might not be back in the swing of things properly - so beware. table_info maps to the ODBC API SQLTables in DBD::ODBC. DBI seems to have picked some