Re: How do I browse a database ?

Jerry,

> You'll have to look at the table itself. No table *requires* a primary > key, but it's always a good idea to have one.

[Quoted] Agreed. But /not/ having one makes it impossible to add it to the end of a selection clause. :-( I've still got to figure out how to handle such tables.

>> Than again, I just ran into this:

...
> Sorry I can't help you here.

[Quoted] After some experimenting it turned out to be embarrassing simple, namely this: "LOWER(id)". It causes the values in "id" to be converted to strings (supposedly causing the "id" results from the table to be converted into strings before sorting too), giving weird end results. I could imagine MySQL having the same problem (nudge, nudge .. does it ?)

> You may be thinking of the ORDER BY clause, which can use comma separated > column names.

[Quoted] Initially, yes. But I verified (or at least tried to verify) the WHERE usage on that webpage I posted the link to.

> And there is no default sort order in SQL. If you don't specify ORDER BY > the sort order is undetermined.

[Quoted] I ment the in-order checking of the comma-seperated equations of the WHERE clause, stopping on a non-equal comparision result. A form of an implicite AND with a "sudden death" checking termination.

You ofcourse realise that as you say that that doesn't work that way that I will, after I got the basic browsing to work, try it out. :-)

> That is the definition of an expression, not sort criteria.

[Quoted] An expression as mentioned in the WHERE branch of the below image:

https://www.sqlite.org/syntaxdiagrams.html#select-stmt

Below it are a "used by" and "references" list of links, from which I selected the "expr" one (duh :-) ). And thats the one I posted. Your honor, is that an adequate chain of evidence ? :-) (please do tell if I'm wrong there though)

Regards,
Rudy Wieser

"Jerry Stuckle" <jstucklex_at_attglobal.net> wrote in message news:qipsvu$o0s$1_at_jstuckle.eternal-september.org...

> On 8/11/2019 3:04 PM, R.Wieser wrote:

>
> You'll have to look at the table itself.  No table *requires* a primary 
> key, but it's always a good idea to have one.
>
> But I also wouldn't worry too much about using a lot of resources - SQLite 
> is good for quick data but not very good at handling large databases. 
> Other databases are much more capable.
>
>

>
> Sorry I can't help you here.  As I said - it's been a LONG time since I've 
> used SQLite.  Well over a decade at the least.
>

>
> So, if the WHERE clause has multiple conditions they must always use 
> boolean operators between the conditions.  You may be thinking of the 
> ORDER BY clause, which can use comma separated column names.
>
> And there is no default sort order in SQL.  If you don't specify ORDER BY 
> the sort order is undetermined.
>

>
> That is the definition of an expression, not sort criteria.
>

>
>
>
> -- 
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> jstucklex_at_attglobal.net
> ==================