|
Take a look at this blog post: http://vaultofthoughts.net/IComparableVsIComparer.aspx[^]
Essentially, IComparer allows you to customize the sort order of a collection by implementing a Compare method that allows you to compare any two arbitrary objects to determine if one is less than, equal to, or greater than the other.
IComparable is usually implemented by types whose values can be ordered (like string and int), but only allows you to compare the current instance with another object using the CompareTo method.
-----------------------------
In just two days, tomorrow will be yesterday.
|
|
|
|
|
Richter (CLR Via C#, Second Edition) has an interesting little chapter on p. 141.
Its title is, "Changing Fields in a Boxed Value Type by Using Interfaces (And Why You Shouldn't Do This)"
|
|
|
|
|
PS. You find that chapter by looking up IComparable in the index.
|
|
|
|
|
Hi,
Anybody can please help me out in getting the data from two different tables in two different databases.
Thanks in advance.
rr
|
|
|
|
|
AR Reddy wrote: Anybody can please help me out in getting the data from two different tables in two different databases.
If you can get data out of one table in one database then it doesn't take any lateral thinking to extend that two tables in different databases.
You open two connections, and execute two commands and you get two sets of results back.
|
|
|
|
|
Depending on your DBMS, you can just reference a different database. For SQL Server, you can do the following.
USE Database1 GO
SELECT *
FROM Table1
SELECT *
FROM Database2.dbo.Table2
You need to specify [Database].[owner].[Table/object]
Hogan
|
|
|
|
|
I have to get into a single database and dind to a dataset. How Can i do this?
rr
|
|
|
|
|
Please provide a bit more information. Name your databases and tables for the example you need.
database1.Table1
Database1.Table2
That sort of thing and then try to describe how you need to get the data out.
Hogan
|
|
|
|
|
DataBase1.Table1
DataBase2.Table2
I want to get the data from above two tables into a single dataset and bind to datagrid.
Thanks,
Reddy
rr
|
|
|
|
|
Reddy,
Start with the query for getting the data. I'll assume your SQL connection is to Database1
SELECT T1.*,
T2.*
FROM Table1 T1
INNER JOIN Database2.dbo.Table2 T2
ON (T1.ID = T2.ID)
With the query above, you can get any data out of the two tables in different databases.
Hogan
|
|
|
|
|
Hogan,
I got it. Thanks a lot.
Reddy.
rr
|
|
|
|
|
Hi i am trying to filter a datatable on a specific sessionID and if a colun is empty/null whatever but i cannot seem to fnid the correct syntax to check if my cell is empty alseo some of the different cols are nvarchar so if anyone knows how to go about doin this or is there a better way to do it any help is appreciated
string queryString = "SessionID = '" + iSessionID + "' And " + sColName + " != ' '";
if(iTable.Select(queryString).Length > 0)
return true;
else
return false;
Thanks
Tim
|
|
|
|
|
The query string is SQL syntax not C# syntax, so sColName IS NOT NULL should do the trick.
|
|
|
|
|
How do I make my status bar functional in C#.net 2005 e.g dividing into panes, displaying info based on current action of the app.
Banjo Ayorinde
|
|
|
|
|
Write a javscript for it
function callFunction()
{
window.status="Come On i am here";
}
call this function in html body load to see your text in status bar
<l>Thanks and Regards
Sandeep
|
|
|
|
|
In all my applications, every time i used something like a FileStream, when i finished using it i called:
<br />
fs.Flush();<br />
fs.Dispose();<br />
fs.Close();<br />
I'm wondering, what's the difference between flushing and disposing or just closing? what's the most efficient way of doing it?
|
|
|
|
|
|
OK
FileStream reads the content in bytes
fs.Flush()-> method clears the buffer which is used by fs while reading or writing
fs.Dispose()-> make the object ready for Garbage collection no instance in Memory
fs.close()-> Only close the fileStream without doing anything
<l>Thanks and Regards
Sandeep
|
|
|
|
|
well, then, i can use dispose instead of flush and close? or flush and dispose without close? o_O
|
|
|
|
|
Its good practice to flush the buffer before closing the stream
after closing the you can call dispose method .
while writing if you forget to call close then it will not save the file which you are manupilating
<l>Thanks and Regards
Sandeep
|
|
|
|
|
no, you can't dispose after you close...you have to dispose before (if you dispose after you close it throws an exception)
|
|
|
|
|
Sorry you are write
Calling Dispose allows the resources used by the Stream to be reallocated for other purposes.
Flushing the stream will not flush its underlying encoder unless you explicitly call an implementation of Flush or Close. Setting AutoFlush to true means that data will be flushed from the buffer to the stream, but the encoder state will not be flushed. This allows the encoder to keep its state (partial characters) so that it can encode the next block of characters correctly.
Closes the current stream and releases any resources (such as sockets and file handles) associated with the current stream
Taken from MSDN 
<l>Thanks and Regards
Sandeep
|
|
|
|
|
sharpiesharpie wrote: if you dispose after you close it throws an exception
If it does, it's a bug in the implementation. You should be able to call Dispose any number of times, and if the object already has been disposed, it should ignore it.
---
single minded; short sighted; long gone;
|
|
|
|
|
Hi,
IMHO:
Flush() is meaningful only if you dont plan on closing right away; it means "send this
through, before I produce more".
I use Flush() when tracing a program's progress to a file, so when the program suddenly
crashes, the file contains all traces including the very last that was called.
FileStream.Dispose():
on .NET 1.1 only exists as Dispose(bool) and is protected, you cant call it;
you should call Dispose() for each object that offers a public Dispose(), but you cant
call a protected one (unless you are inheriting from the class).
on .NET 2.0 exists and is public but the doc says "is not intended to be used directly
from your code", so dont call it !
Close() is the one that MUST be called, it tells everything is done. And according to
the doc it calls Dispose(bool) itself.
Conclusion:
call either Flush() if you plan on producing more but want to make sure what you already
have gets processed, or Close() if you're done. Dont call both.
BTW looking at the (current) implementation is not a sound base for deciding what
function to call, reading the doc is.
|
|
|
|
|
sharpiesharpie wrote: fs.Dispose();
fs.Close();
Close and Dispose in this class are synonyms of each other - they do the same thing.
As implemented, Close() calls Dispose() which, in turn, calls Flush()
Flush writes out anything remaining in the buffer to the file.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
