Re: [sqlite] Free tool to visualize a schema?

Unfortunately SQLite does not fully support introspection. On Sun, Apr 15, 2018 at 7:52 PM, Csányi Pál wrote: > Hi, > > I think the visualization of a schema helps to develop a sqlite database. > > I am searching for a free software, like SchemaCrawler. > It is good, but

Re: [sqlite] How many AUTOINCREMENT tables are in your schema?

When needed I use a declared INTEGER PRIMARY KEY. > > MAYBE THAT WOULD HAVE BEEN IN THE SURVEY TOO BUT I GUESS THERE WAS NO WAY TO INCLUDE A SMALL PIECE OF SQL TO RELIABLY CHECK FOR INTEGER PRIMARY KEY YES I AM SHOUTING ___ sqlite-users mailing list

Re: [sqlite] Any chance of exposing INTEGER PRIMARY KEY metadata? Needed by many tools

egacy to support. But you can do that without fucking over tool developers and all the users who use or wish to use those tools such as myself. Thanks for listening. Peter Halasz. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http

Re: [sqlite] Any chance of exposing INTEGER PRIMARY KEY metadata? Needed by many tools

e an integer. https://www.sqlite.org/src/timeline?p=2494132a2b1221a4 On Wed, Nov 29, 2017 at 1:24 PM, Peter Halasz <pe...@becauseofgames.com> wrote: > That's terrific! Looking forward to it being in a full release. > > Hopefully the next tool developer to come along won't need to wr

Re: [sqlite] Any chance of exposing INTEGER PRIMARY KEY metadata? Needed by many tools

r virtual > table or if it does not exist, then return no rows. > > The lesson here is that one may safely ignore the sometimes authoritative > sounding status quo mafia who occupy this mailing list but have no source > check-in credentials whatsoever. > > On Mon, Nov 27, 2017

[sqlite] Any chance of exposing INTEGER PRIMARY KEY metadata? Needed by many tools

Disclaimer: I am not a developer on linq2db. Nor am I a developer on "DB Browser for SQLite", nor am I a developer of any of the other tools which help developers create SQLite databases and integrate them with their projects through UIs and APIs built on SQLite and its metadata. However, it's

Re: [sqlite] "BIGINT" doesn't act like INTEGER on table creation [Bug]

Is this a joke? ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] "BIGINT" doesn't act like INTEGER on table creation [Bug]

> sqlite> .load column-meta-data.so Sorry I'm at a loss to find this extension? Google gives me nothing related to SQLite for "isRowId", "column-meta-data.so", "column-meta-data.c", etc. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] "BIGINT" doesn't act like INTEGER on table creation [Bug]

Sorry to steer the conversation back to the topic. Looks like I do need to use AUTOINCREMENT after all, otherwise the framework I'm using doesn't appear to recognize that INTEGER PRIMARY KEY columns are allowed a NULL value on insert. That's a shame. Is there a way to query a schema to get a

Re: [sqlite] "BIGINT" doesn't act like INTEGER on table creation [Bug]

Thank you. It looks like I was looking at the wrong documentation page. So I will reiterate and clarify my advice that the datatype documentation ( https://sqlite.org/datatype3.html), within the section on "Determination Of Column Affinity", should more clearly state the fact that the affinity

[sqlite] "BIGINT" doesn't act like INTEGER on table creation [Bug]

BIGINT has a "resulting affinity" of INTEGER ( https://sqlite.org/datatype3.html) but cannot be used in its place in the following example: CREATE TABLE [FailTable] ( [id] BigInt PRIMARY KEY AUTOINCREMENT ) ...as it gives this error: AUTOINCREMENT is only allowed on an INTEGER PRIMARY