Re: [IBMiOSS] Queries over ODBC not always the same as in STRSQL?

Is it a limitation of ODBC, or SQL. SQL ( keep in mind my SQL skills are limited) sees members as partitions of the table, does it not?

Looking for files with attribute ‘pf-src’ will find all the source files. Easily done in CL. Now you can use simple CL commands to get the member count.

Sounds more Like a CL problem than SQL to solve.

Jim Oberholtzer
Agile Technology Architects

On May 21, 2021, at 10:16 AM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

I was trying to get the number of members in various source physical files.

So I whipped up a little Python script containing the following SQL:

select count(*) from qsys2.syspartitionstat
where table_schema = ? and table_name = ?

For some files, this works fine. For others, it (very quickly) returns
0, even though there are definitely members. This happens whether I'm
running from my PC or from PASE. The same SQL works fine in STRSQL for
any file I've tried.

If there is any pattern to it, it seems the files with a lot of
members (say, over a couple thousand) come back as empty over ODBC.
Files with a smaller number of members work fine with both ODBC and
STRSQL.

Has anyone else noticed this? Is it a limitation of the ODBC driver?

John Y.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com