Friday, September 16, 2011
Subscribe to:
Post Comments (Atom)
skip to main |
skip to sidebar
SQL Anywhere® Does Things The Way They Should Be Done.
Search this blog...
-
▼
2011
(226)
-
▼
September
(23)
- The fRiDaY File - Quiz Week!
- Let's play "Gotcha!" - Round Three
- The Thursday Quote - Jason Hong
- Let's play "Gotcha!" - Round Two
- Let's play "Gotcha!" - Round One
- The fRiDaY File - "Fuji - that's in Japan, right?"
- Fuji Watch
- The Thursday Quote - Brian Dorn
- Latest SQL Anywhere EBF: 12.0.1.3436 Windows
- Smithsonian Anywhere
- The fRiDaY File - Life Before "Fuji"
- "Fuji" is the SQL Anywhere OnDemand Edition
- The Thursday Quote - Kevin Benedict
- The Morning After
- OLAP Counseling
- The fRiDaY File - Impostor Syndrome
- Next Week is Fuji Week at Techwave
- The Thursday Quote - Rudy Rucker
- Unrequited OLAP
- What a great idea!
- The fRiDaY File - "Drinks for everyone!"
- Wishing for a WER
- The Thursday Quote - Kinshuman Kinshumann
-
▼
September
(23)
Categories
- announcement (275)
- Database Deadpool (10)
- database migration (2)
- Design (2)
- Did You Know (2)
- Dilbert (83)
- Dilberts (1)
- Foxhound (59)
- HANA (5)
- housekeeping (14)
- latest EBFs (95)
- off topic (30)
- patches (1)
- performance (1)
- performance and tuning (72)
- server setup and admin (80)
- SQL code (241)
- SQL search (2)
- SQLA (11)
- testimonial (62)
- The fRiDaY File (87)
- The Thursday Quote (21)
- xkcd (1)
5 comments:
...that's why Breck doesn't like NULL that much, isn't it?
(I stumbled over the same error message yesterday.)
Volker
What were you trying to download when you got the message?
@Eric Farrar: On Friday I was trying to answer the question "what was last EBF for SQL Anywhere 9?" but that is not important: the error was a showstopper preventing ALL use of the Sybase download page. It was a moment of serendipity, albeit transient, because it allowed me to add material The Friday File before it appeared in public. It was transient because the error was gone by the time I needed the download page again a day later. Once upon a time this kind of thing was frustrating, but the secret to true happiness is to lower one's expectations :)
@Volker: Well, at least the diagnostic message was thorough enough to point out that a null WAS involved... but was it a "nul-terminated string" or a "database NULL"? Both are evil IMO, and it's hard to say which one has caused more heartache over the years.
@Eric, @Breck: FWIW I noticed the error message in the exact same situation - I bet Breck and me wanted to answer the same SQL Anywhere forum question... I guess it worked again some minutes later.
@Breck: Having worked with C/C++ and SQL for years, I still accept both "NULL concepts". Though I would claim that SQL's three-valued-logic has lesser (if any) "smart" alternatives.
That being said, both have caused headaches now and then, too:)
Regards
Volker
Post a Comment