From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Regression tests for functions of info.c |
Date: | 2014-03-13 14:20:58 |
Message-ID: | CAB7nPqTUY1MShmedz4=p8-Qa_zk5My=xNv=e5BVvqQ9EF2_Tiw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On Thu, Mar 13, 2014 at 11:01 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> Hmm, that's fine as far as it goes, but surely we need to test that they
> actually return correct data, not just the column names?
The point of this test was to cover the issue related to the column
names: e: http://www.postgresql.org/message-id/5315E622.2010904@ntlworld.com.
If we want to test all those functions by checking their data, we will
need roughly to either choose and/or create one/two table(s) with pk
and fk, a procedure, a data type, and an index for SQLStatistics. I
imagine that raw data will be more helpful than querying catalog in
this case except for the data type.
> I envisioned the "catalogfunctions" test case to eventually cover these,
> although at the moment it only tests SQLTables. The ODBC standard calls
> these "catalog functions", per
> http://msdn.microsoft.com/en-us/library/ms711722%28v=vs.85%29.aspx. From
> that list, you're missing SQLColumnPrivileges and SQLProcedures.
I lack of caffeine.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-03-14 07:06:11 | Adding flag LDFLAGS for compilation of regression tests |
Previous Message | Heikki Linnakangas | 2014-03-13 14:01:32 | Re: Regression tests for functions of info.c |