Not exactly sure of the OP's full issue.
This does arise on occasion though, especially for when you try to maintain
a self-sustaining database. Ignoring the API for a moment, there is some
rationale for keeping metadata available for use. My primary use is as a
CLI toolkit, if not as a desktop workbench to convert data.
If there's pragmas like table_info available...can these be made available
for parsing, or used as virtual tables for selection, etc? (These could
facilitate some of the metadata questions, probably without much overhead,
to my knowledge at least.)
I love that sqlite_master can be wrangled to an extent; I can generate sql
to get table counts en masse, for example, but not without passing the
generated sql between UIs. If there's a tabular option available, it would
eliminate external reliance on code, if not simulate dynamic sql in some
On the other hand, if I am missing something in front of my face...I'm sure
that someone here will make me aware.
Brian P Curley
On Feb 23, 2018 1:06 PM, "R Smith" <ryansmit...@gmail.com> wrote:
> On 2018/02/23 2:46 PM, M wrote:
>> sqlite has an integral problem, field names cannot be selected each one
>> inside a program, there is way to do it, but it is not straight and
>> complicates the software programs, and makes the program complicated and
>> not readble.
>> when you try to do something with the selected fields/columns, a lot of
>> code can be reduced, if only there where field names - the ability to work
>> with them directly.
> Let me get this straight: Are you saying the query "SELECT Field1, Field2,
> Field3 FROM myTable;" does not work for you, but "SELECT * FROM myTable;"
> or, are you saying that both queries work fine, but you have no way of
> telling what the names (Field1, Field2, etc.) are once you receive the data?
> Both of these are of course utterly possible in SQLite and required in
> principle by any SQL RDBMS system - so if possible, could you perhaps post
> some small bit of code that illustrates what happens for you and say what
> it is that you expect to happen/be possible but that isn't working (even
> perhaps code that works for MySQL/PostGres/etc.). Anything to make more
> clear what you mean so we will be able to show how it works in sqlite.
> Kindly also mention your programming platform, OS and any other relevant
> information you can think of. The more you say, the easier for us to help.
> sqlite-users mailing list
sqlite-users mailing list