The Heap™ – Consultancy ©®

Andriy M

4:57 AM

@PaulWhite Too much honour, you mean? Yes, it is. :)

But seriously, you are expanding on a point I completely missed.

Paul White

I'll leave it as it is then. Cool.

15

A: Best way to write SQL Query that checks a column for non-NULL value or NULL

This pattern column = @argument OR (@argument IS NULL AND column IS NULL) can be replaced with EXISTS (SELECT column INTERSECT SELECT @argument) This will let you match a NULL with a NULL and will allow the engine to use an index on column efficiently. For an excellent in-depth analysis of ...

Colin 't Hart

8:42 AM

G'day

Tom V

goeiemiddag

ConcernedOfTunbridgeWells

9:24 AM

Morning all

@swasheck You're confusing it with the language people use to describe it.

2

dezso

12:21 PM

afternoon

can one somehow figure out how accepts suggested edits?

this user adds tags, without (nearly) ever fixing anything else:

oNare, Santo Domingo, Dominican Republic

1.6k 1 2 20

Tom V

I've seen him before :)

he's after rep before anything else

many answers every day, a lot of them 0 score, very late, ...

ypercube

@dezso needs some advice - or flogging

Paul White

Badge hunting perhaps. Not a bad thing where the activity adds value, but I agree his contributions have been highly variable. I blame the reviewers ;)

Actually, quite often the author of the question accepts the edit.

dezso

that's also true

I gave advice in one of my rejection comments

I can imagine he didn't read it

Tom V

he's a student, probably doesn't have anything to do during vacation

:)

dezso

12:33 PM

@TomV too much coffee? (see chat.stackexchange.com/transcript/message/22960288#22960288)

Tom V

@dezso that, and working with a PFE at the moment

dezso

@TomV Pfizer@NYSE?

dezso

12:56 PM

kick this back to SO, please

0

Q: postgres could not connect to server: No such file or directory in ubuntu 15.04

when I run postgres server I am getting the following error psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? I am using kubuntu latest version 15.04 and using pos...

postgresql

you have to start the database in order to connect to it

surprise

and my take on oNare's poor edit: dba.stackexchange.com/posts/107990/revisions

Tom V

@dezso premier field engineer

dezso

1:11 PM

ah, it is something like a fireman, right?

Tom V

1:21 PM

he's the thing you sometimes need to calm your customer down and give them a cozy feeling that their problem has been escalated to the top

dezso

but apparently it doesn't calm you down, right?

Tom V

the fact that he calms the customer down allows me to work on the problem at hand

which is solved by now

dezso

ah

that it sounds a win-win

Tom V

it is

it's a whole different level of quality than their support engineers

so the comment was more "working with a PFE" = "not really a laidback friday"

Marian

1:42 PM

@TomV I know one, too

same opinion as yours, a brilliant gal

Colin 't Hart

2:19 PM

@AaronBertrand I don't understand some of the syntax in your answer dba.stackexchange.com/a/108013/10361

1. Why do you have "column = func(column)" in the select clause?

In PostgreSQL that would return a boolean...

2. Why (and I've seen this elsewhere before) do you have a semicolon before the with?

bluefeet

@Colin'tHart the "column = ..." is a way to give an alias in SQL Server

Marian

@Colin'tHart CTEs have this funny syntax requirement

Colin 't Hart

WTF+

That's so silly...

Both requirements, but I was primarily reacting to the "a = expr" syntax

Marian

"with" keyword has multiple uses (hints, CTEs), this one helps differentiate for the CTE

@Colin'tHart it's Aaron's prefered way of aliasing columns

Colin 't Hart

I think it's a braindead design.

You can have two expressions in one query -- one in the select clause and one in the where clause -- having entirely different semantics.

Paul White

2:26 PM

@Colin'tHart WITH requires the previous statement be terminated properly. Putting a semicolon before the WITH guards against that not being the case. Ok I suppose for demo code, not something I would do in production code.

Colin 't Hart

@PaulWhite Aha, That makes more sense to me.

Paul White

alias = expr reads nicer to me, you don't have to scan right to the ragged edge to see the exposed column name. By all means use expr AS alias if you prefer. Style thing.

Jon

anyone have any recommendations for SQL Server Training? Looking at the Microsoft training offered here: microsoft.com/learning/en-us/sql-training.aspx and wondering about the quality?

ypercube

@Marian It's not a requirement of CTEs really. But it may give syntax errors if the previous statement is not terminated with ; because of the similar WITH NOLOCK hints/syntax

Aaron Bertrand

@Colin'tHart Yes, exactly as Paul suggests (I even blog about it). I don't write code for PostgreSQL and don't really place portability above all else - I'll use ANSI standard when it isn't more convenient to do otherwise. I blogged about this here:

sqlblog.com/blogs/aaron_bertrand/archive/2012/01/23/…

@PaulWhite I do that even in production, to avoid someone pasting in some query or statement before the CTE and then complaining when it breaks

Marian

2:34 PM

@ypercube indeed, lazy wording, it's as Paul said, previous statement needs to be terminated correctly with a ;

Paul White

@AaronBertrand Yes, fair enough.

I'm not that nice :)

Aaron Bertrand

@ypercube And you can never have too many semi-colons. This is valid: SELECT 1;;;;;;;;;;;SELECT 2;;;;SELECT 3;;;;;;;;

Transcript for

The Heap™ – Consultancy ©®