DEV Community

Discussion on: I did it again.

Collapse
 
kspeakman profile image
Kasey Speakman

I do this too! We're using pgAdmin, and sometimes it crashes and I haven't bothered to save the query. Most of the time I'm using it, the queries are only needed for a short while, so not a big deal. But that one time I am using it to prototype developing real queries and don't save is when pgAdmin crashes and I have to start over.

Collapse
 
phlash profile image
Phil Ashby • Edited

Auto save if your tools have it.. otherwise train that Ctrl-S reflex!

On the boolean logic front - I always try to use positive logic everywhere, I get uncomfortable when the nots start appearing, especially review others code.

Thread Thread
 
kspeakman profile image
Kasey Speakman

My normal workflow with those tools doesn't need to save anything, and doing so is extra time spent for otherwise quick work. So in effect, needing to save something goes against my training. And unfortunately pgAdmin doesn't have auto-save. When actually developing a query I probably just need to open Notepad++, which does have autosave, and set the Language to SQL. Then copy paste it to pgAdmin to run it.

I think using only positive logic is not really achievable (unless I have mistaken your meaning). The code that tripped me up was this.

    let hasToken nextToken =
        not (System.String.IsNullOrWhiteSpace nextToken)

IsNullOrWhitespace is a positive check. hasToken is a positive check. But I need a not to turn one into the other.

Thread Thread
 
phlash profile image
Phil Ashby

Ah ok, I get the normal workflow thing - similar here when tinkering in SSMS or similar, and I've been bitten by a crash doing that too.

I don't think you mistook my meaning on positive logic, although I used the phrase "always try" as sometimes it can be impossible (thanks random APIs!)