@eden: "<quote>
    Craig> I just wish they hadn't written it backwards!
    Craig> It'd be much less confusing were it formulated as something
    Craig> like:
    Craig> SELECT FROM thetable WHERE first_letter > 'a' RESULTS
    Craig> left(value,1) AS first_letter
    Craig> or something, where the order is more obvious. I really
    Craig> dislike the way SQL is written not-quite-backwards.
It's not "written backwards", it's plain natural language semantics:
"give me the first letter of all records where the first letter is
greater than a". Refining a set is better done walking from the more
general set to a subset, not the other way around, IMO: "give me all
persons that are females and over the age of 20". Mathematical set
builder notation does this in a similar fashion, for the same reason.
Eden Cardim
<url>
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @mike: "<quote>
Oh no, this debate again..
I do admit LINQ kind of threw me for a loop as they took the other
approach (from f in foo where f.id > 5 select f), which makes you
think about the collection you're working with first.  I usually think
about the table first when I'm writing a query.
I can also say if the table came before the columns, we'd probably
have a lot more SQL editors with auto-complete that worked :)
Mike
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @eden: "<quote>
    Mike> I can also say if the table came before the columns, we'd
    Mike> probably have a lot more SQL editors with auto-complete that
    Mike> worked :)
There's nothing stopping an editor from making you type the table
first though, it's easier to implement that in an editor than it is to
change the way people have been thinking about math for the last few
of centuries.
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @mike: "<quote>
No, I meant editors that auto-complete SQL statements for you as
you're typing them.  Like Intellisense in Visual Studio.
Obviously you wouldn't want to type "select " and then see a list of
every column in your database, since it doesn't know what table you
want yet.
Mike
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @eden: "<quote>
    Mike> No, I meant editors that auto-complete SQL statements for
    Mike> you as you're typing them.  Like Intellisense in Visual
    Mike> Studio.
    Mike> Obviously you wouldn't want to type "select " and then see a
    Mike> list of every column in your database, since it doesn't know
    Mike> what table you want yet.
Again, you can type "select" and the have the editor expand the whole
thing into "select _ from [cursor is now here]" and present you with a
list of tables for the autocomplete, then after you've selected the
table, it goes back to the field part of the query. I have emacs
rigged to do this with yasnippet, except that it relies on a
handwritten function, not intellisense. Point stands, easier done in a
single editor as opposed to changing the semantics of math.
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @rod: "<quote>
Really? I haven't used Irish seriously since I left school - maybe I
should learn Lisp.... :-)
Ray.
Raymond O'Donnell 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 Galway 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 Ireland
<email_address>
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
{'source': 'USENET', 'other_information': '{"reply_count": 5, "forum_name": "pgsql.general.20140707.mbox"}', 'file': 'data/output/usenet-pgsql.general.parquet'}