The Cellar - This is the title of the thread

The Cellar (http://cellar.org/index.php)

- Nothingland (http://cellar.org/forumdisplay.php?f=36)

- - This is the title of the thread (http://cellar.org/showthread.php?t=22863)

This is the title of the thread

And this is the first post in the thread.

This is the end of the thread.

This is an attempt to get the thread back on track after its rough beginning. In it, I attempt to relate my own experience to the original post.

In this post, I say something appreciative towards the previous poster, and make a reference to that move trailer where the people do just what is going on here.

I laugh fondly at the memory that movie trailer, and go seek it out on Youtube to watch it again. I briefly consider posting the actual trailer to the thread, but decide that would be overkill. Instead, I relate a personal anecdote with relevance to the original post, which is somewhat similar to Undertoad's experience, but comes at it from a different angle.

I misread your post taking it as a personal insult. My reply bears no relevance to the topic and leaves many scratching their heads, looking for a connection.

And there she was at the swimming hole trying to teach her kids how to swim against other kids.

Meanwhile, we were living in a hole in the very same lake.

In this post I go off on the merc for not conforming to the meme of the thread....but in an ironic twist, come out looking like a bigger jerk then him. Also, I make a grammatical error.

In this post I make a completely sarcastic and slightly obscure and overboard retort. Then I realize it and laugh at myself, out loud. Then I have to add a smiley to show I was breezy. :lol:

The title of this thread is offensive to me. Have you no compassion? Now I'm going to cry. See what you made me do?

In this post I point out that Merc merely posted in the wrong thread.

I then suggest that I misplaced a post on 9/11 and express my contempt, hoping to rescue myself from my previous error by implying that I was just kidding.

I am Quite outraged in this Post. Due to your lack of Compassion, by misplacing a post, for my lizard That died in or on 9/11.

In this post I do the sarcastic eye rolly thing and wonder how we can slide into the 911 meme so quickly. Then I notice it was the 13th post. I am not superstitious but it is a good reason for any for thread failure.

The name of this thread is The Talking Threads.
(This is not your clever thread, these are not your beautiful threads)

Puh, yeah. This thread is the same as it ever was.

Having not bothered to read any of the preceding posts, I write a bad poem and link to a post that I wrote two years ago, in a style now outdated, hoping to bring attention to myself.

This is the post were I point out the ovbuse and make a non sequestrate comment for a cheap chuckle,

Tautology thread. Never not true

This is the application for a corrected title

Quote:

Originally Posted by lumberjim (Post 660287)

This is the title of the thread
--------------------------------------------------------
And this is the first post in the thread.

And this is the first quote in the thread.

In this post I wander in a bit late, and attempt a play on words referring to a previous post. It isn't very funny.

I do a quick google search and relate everything to the political spin involved in the subject.

I fall for the troll and begin to compose a post in response, but come to my senses and delete it without posting.

This is the post where I go into a serious thread and try to be comedic and end up posting something trite, like "this isn't a thread, it's a dolphin".

this is the post where I point out someone's spelling mistakes--just for their information, of course! I'm not a grammar-you-know-what, no!

This is where I wander in, eating an apple, wondering what the hell is going on and why am I always so late to the party? Then I wonder if I look like an attention whore and whatever happened to mari - did she starve to death in colorado? Is staceyV still crazy and involved with the russian mafia?

Then I get nostaglic.

This post contains the first spam link in the thread

This is the ETA - I inserted the link without actually seeing if it was a real link.

Quote:

Originally Posted by Brianna (Post 660467)

Then I get nostaglic.

This is where I quote Bri, and get nostalgic too. I wonder if Rich still has those razor blades on his thumbs.

This is the first youtube link, and it's also the theme to Garry's show.

Here is where I cut and paste some long-winded only slightly related to anything article, then nod knowingly about how many facts I know, here is also where I bold stuff that I am sure punctuate my point, whatever that is:

Quote:

Much ADO About Nothing
ADO.NET's NULL support answers developers' questions about...nothing

William Vaughn

One item on most developers' wish list is a tried-and-true way to determine the best ways to test for and set NULL values in their applications—regardless of the language the applications are written in. For example, when they need to signify that DateShipped or DateDied dates haven't been reached and aren't known, most relational database developers have to define these and similar data columns to permit NULL values. Note that a NULL value in a data column isn't the same as an empty or NULL string or any other placeholder that can serve to show that the value isn't known. The language you're using can treat an empty string or a placeholder value (such as Unknown) as a string or valid value and can store a NULL as a "known" value in the database. The concept of NULL has been a part of relational databases since their inception, and NULLs have always garnered special treatment. I won't get into a long-winded discussion about the wisdom of using NULLs, but I do think NULL is a better placeholder than BHOM (Beats the Hell Out of Me), which I used when I taught programming for the US Army.

In classic ADO, developers have to deal with NULL values because they can't assign a NULL to a numeric variable, a string, the Value property of a TextBox control, or any control that doesn't accept a variant data type (which you can set to NULL). If you forget to deal with NULL values and try to assign a NULL to a TextBox control, Visual Basic (VB) 6.0 issues an Invalid Use of NULL (94) error message. But ADO.NET and Visual Basic .NET have better support for NULL values. When you're working with the Common Language Runtime (CLR) and the .NET languages, ADO.NET lets you store, set, and test for NULL values in a variety of ways—far more than with classic ADO. This article uses Visual Basic .NET to showcase ADO.NET and Visual Basic .NET's NULL support.

In VB 6.0, if you expect that a field might contain a NULL value that will result in an Invalid Use of NULL error, you can short-circuit the problem by concatenating an empty string to the data Field.Value from the Recordset to the display TextBox.Text property as follows:

txtDateSold.Text =
rsMyData("DateSold") & ""This approach converts NULL values to an empty string, which the user doesn't see. If the TextBox is a bound control, this empty string (which represents a NULL value) is written to the database as an empty string unless you add code to convert the value back to a NULL—a must if the database column data type isn't a varchar or char. Concatenating an empty string also works in Visual Basic .NET, but the user still can't tell the difference between an empty TextBox and one that reflects a NULL value in the database—and you still have to add code to convert the empty string and post a NULL value to the database.

The easiest way to test for a NULL value in VB 6.0 is by testing for the Null keyword, as the following code shows:

If Not rs(0) = Null Then
Text1.Text = rs(0)
Else
Text1.Text = "<Unknown>"
End IfYou can also test for NULL values in VB 6.0 by using the IsNull() function, as the following code shows:

If IsNull(rs("DateShipped")) Then
txtDateShipped.Text =
"<Unknown>"
Else
txtDateShipped.Text =
rs("DateShipped")
End IfHowever, this approach takes a little longer to code and execute because it uses late binding. VB 6.0's IsNull() function corresponds to Visual Basic .NET's IsDBNull() function, which I show in a moment.

Setting NULL Values in VB 6.0
Setting an updateable Recordset Field object's Value property to NULL is painless: You can use either the DBNull or Null keywords, as the following three code examples show:

rs("Author") = DBNull
' The third (2) Field object
' is "Author".

rs(2).Value = Null

rs.Fields(enuFields.Author).Value = DBNullFor this method to work, the Field object must be updateable and support NULL values. All three of the above lines of code produce the same result.

Testing for NULL Values in Visual Basic .NET
Visual Basic .NET (and the .NET Framework languages in general) support many techniques for handling NULL values, as the following code examples show. First, open a connection and run a query to return several columns in a rowset; in this case, the first column is always NULL. To simplify the code, I use the dv variable to hold the returned column value:

Dim dv As Object
dv = drReader.GetValue(0)
' Capture the first value from
' the data stream.
txtDateShipped.Text = "" &
dv.ToStringYou can use any of the following techniques to test for NULL values in a specific item in the ADO.NET SqlDataReader object's Items collection, as I show later—to learn how to use the IsNULL() function to avoid NULLs, see the sidebar "Using T-SQL to Avoid Unwanted NULLs." Note that because I declare dv as an object, dv can contain a NULL value. If I don't declare dv as an object, ADO.NET will produce the exception message System
.InvalidCastException: Specified cast is not valid—but not until the query returns a NULL.

The first technique I use to test for NULL uses the Visual Basic .NET TypeOf function to examine the object data type:

If TypeOf dv Is DBNull Then
txtDateShipped.Text =
"<Unknown>"
Else
txtDateShipped.Text =
drReader(0).ToString
End IfThe next technique compares the data value in dv by using the expression Is DBNull.Value, which returns True if the object referenced is NULL:

If dv Is DBNull.Value Then
txtDateShipped.Text =
"<Unknown>"
Else
txtDateShipped.Text =
drReader(0).ToString
End IfYou can also use the IsDBNull expression to test for NULL against a specific SqlDataReader item; IsDBNull returns True if the column is set to NULL:

If IsDBNull(drReader(0)) Then
txtDateShipped.Text =
"<Unknown>"
Else
txtDateShipped.Text =
drReader(0).ToString
End IfAnd the final technique, which Listing 1 shows, uses the IsDBNull method of the specified SqlDataReader or Rows object, which returns True if the specified column contains a NULL.

Passing a NULL Value Back to the Server
In some cases, you might have to pass a NULL back to the server either as the contents of an updateable DataTable's DataRow or as a parameter in a query invocation. Visual Basic .NET and other languages make this operation easy—but different from what you might be used to. The code in Listing 2 executes the AcceptNullParms sample stored procedure. The stored procedure accepts two input parameters. The first parameter defaults to NULL, so if no parameter is passed, the default value of NULL is applied. The second parameter is required but can be set to NULL in your ADO.NET code (as Listing 2 shows) when you set up the Parameters collection.

The code to execute this stored procedure in Visual Basic .NET isn't complex. Notice that when I set up the Parameters collection, I don't specify a value for the first parameter, so ADO.NET passes default as the first parameter, as the SQL Server Profiler trace below shows. When I ran Profiler on the ADO.NET code that used the DataAdapter Fill method to execute the query, Profiler reported that the following query resulted:

exec AcceptNullParms @DateShipped
= default, @QtyOrdered = NULLI set the second Parameter.Value property to DBNull.Value to pass NULL as the data value, as the code in Listing 3 shows.

When you need to set a data column value to NULL in a DataRow (and the column permits you to set the value to NULL), simply set the object to DBNull.Value:

ds.Tables(0).Rows(0)("ISBN") =
DBNull.ValueAs more developers wade into ADO.NET, the number of questions about nothing—that is, about handling NULLs—is increasing proportionately. Fortunately, ADO.NET and the .NET languages provide far better support for nothing (er, NULL) than ADO and VB 6.0 do.

Here is where I show the link.

Here is where I seem pensive and thoughtful as I wonder, hmmmm, what do they actually MEAN by 'support' and 'approach' and venture so far as to say it's Obama's fault.

This is the post where I call all you fuckers a name. Fuckers.

Cite

Something.

Fail.

That is all.

Witty post with obscure reference.

This is where Pete must've stolen one of MY posts.

This is where I post a picture of my cat in a cake box.

This is the post where I ask what the funk goes on, in the minds of you people. :eyebrow:

This is where I post my thoughts on how cute gravdigr's cat in a cake box is. I also make some reference to basement cat, and evil world takeover.

This is the post where I ask for the link to ceiling cat cuz digr and mtp reminded me of shim.

This is the post where I test the depth of the thread by shouting into it ... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

Quote:

... HELLO!

This thread is deep.

This is the post with the guy, who's been here off and on for years says:

[Keanu]Whoah! This is so meta![/Keanu]

And everybody goes and checks his stats and sees that, yes, he's been here awhile...but he doesn't say much.

Post #30 is the last post.

Yes, yes it is. Or should be.

A reminder that you're a piece of crap not worthy of breathing let alone posting.

(No, not you) ;)

Followed by:

You're passive-aggressive!!!!1!

:lol:

Quote:

Originally Posted by sexobon (Post 660598)

This is the post where I test the depth of the thread by shouting into it ... HELLO!

This thread is deep.

Hi!

Quote:

Originally Posted by TheMercenary (Post 661947)

Hi!

No, I stopped doing drugs last week. :p:

(picked up from a Gp. Surgeon who used this response when people said "Hi Doc!")

At a factory where I worked it was loud and I would have entertain myself by shouting to my bosses "How, high are you?" instead of "Hi, how are you?"

I'm easily entertained.

I don't know where that 'have' came from...^^^

This is where I needlessly point out that Gravdigr is on some high-octane coffee.

Heheh...coffee yeah.