|
Frans bouma has something to say about stored procedures here[^]. It's worth reading.
|
|
|
|
|
Thanks, I've been looking for that article for a while. Read it several months ago.
|
|
|
|
|
Togakangaroo wrote: fewer applications to maintain
SP can be harder to maintain, as it's not contained in a visual studio like solution or project. You literally have to search through all 150 SPs to find business logic, and the capability of renaming of column doesn't help.
|
|
|
|
|
Just use LINQ 
|
|
|
|
|
Amen to that my brother 
Harvey Saayman - South Africa
Junior Developer
.Net, C#, SQL
you.suck = (you.passion != Programming)
|
|
|
|
|
I'm wondering whether or not Linq is the new embedded-SQL, I might be interested if so.
|
|
|
|
|
I have personally made it my mission to get rid of all but needed stored procs by using LINQ. And guess what, tomorrow I can swap to Oracle* or MySQL* and use the same code!
* Given they have working LINQ query providers.
|
|
|
|
|
I, like a lot of people, use stored procs extensively, mostly on reasonably large databases. Some of the reasons:
Network performance - why push extra data over the network (sp name + parameters as opposed to long sql statement)
Reuse, maintainability and consistency - if you have two applications doing the same query (perhaps with complex joins) and you need to change the query you change (and release) 1 proc, not 2 applications. You also ensure that all versions of the query are consistant and performance tuned - different developers have different skills, not everyone is good at sql.
Performance - I know that paramterised queries are cahced etc, but there are more opportunities for tuning with stored procs (some people may dispute that, thats their opinion)
There are other pros and cons, and everyone has differing opinions. I am possibly biased in that I have been contracting (mostly at large international financials) for many years, and all PRODUCTION applications have to access the database using stored procedures. This simplifies upgrades and bug fixes as you roll out a stored procedure to 1 server (possibly replicated) rather than several applications to users around the globe.
Bob
Ashfield Consultants Ltd
|
|
|
|
|
Ashfield wrote: reasonably large databases
It's the statement that matters, not the size of the database.
Ashfield wrote: as opposed to long sql statement
You only need to do that once per application run.
Ashfield wrote: 1 proc, not 2 applications
One DLL, not two EXEs.
Ashfield wrote: users around the globe
Web Service?
|
|
|
|
|
PIEBALDconsult wrote: It's the statement that matters, not the size of the database.
Not totallly, you can get anyway with any old crap on small databases, but I only mentioned database size as background.
PIEBALDconsult wrote: You only need to do that once per application run.
What, even a paramaterised query?
PIEBALDconsult wrote: One DLL, not two EXEs.
Still have to deploy to all users
PIEBALDconsult wrote: Web Service?
Performance?
Sorry, eveyone is entitled to their opinion, I am merely giving my two pennth based on my experience. Other people, as I said, have different opinions and I am fully aware that the financial industry differs in working practices from other industries.
Bob
Ashfield Consultants Ltd
|
|
|
|
|
Stored procedures are great, but they are not magical.
You might sometimes get a slight speed benefit from using stored procedures, but the potential is very limited. You can easily get much more speed from other changes.
If you want to keep as much of the programming as possible in one place, the database is definitely not the place. Robust and maintainable code is better written in a compiled and object oriented language. Your stored procedures should query data, and little more.
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
I gave you a 5 even though I don't agree with
Guffa wrote: stored procedures should query data
|
|
|
|
|
I use store procedures a lot, never thought it´s a bad idea.
It makes my work better organized.
Good Luck
nelsonpaixao@yahoo.com.br
|
|
|
|
|
Hi,
I have build a class with a Thread as a member. The thread's function is also defined within the class and I start the thread at the class' constructor. - So far so good ...
Now my question: I created a instance of this class and I've noticed that the internal Thread keeps running after the class instance goes out of scope.
I can see that the only way to stop the Thread is to implement a "public Teminate()" method that kills the Thread.
I wanted to implicity shut down the internal Thread so I tried to implement Finalizer. this didnt work for me - the Internal thread kept running and the Finalizer never called
Any ideas how to solve this issue? It also interesting to know why such behvior occures.
Many thanks!!
Ofer
|
|
|
|
|
ofeririko wrote: Any ideas how to solve this issue?
Yes. I suggest you start here[^]. After you have exhausted that resource there are many, many others available on the internet on this subject.
led mike
|
|
|
|
|
ofeririko wrote: I created a instance of this class and I've noticed that the internal Thread keeps running after the class instance goes out of scope.
Yes, mainly for two reasons.
1. A thread doesn't die just because there is no reference to it's class. It's referencing the class itself, so it's not going to be garbage collected.
2. Nothing happens to the object when the variable referencing it goes out of scope. Absolutely nothing. When an object becomes unreachable it's up for garbage collection, but the garbage collector doesn't care about scope at all, only usage. The concept of scope is only relevant to the compiler.
ofeririko wrote: I can see that the only way to stop the Thread is to implement a "public Teminate()" method that kills the Thread.
The well behaved way of stopping a thread is to tell it to stop, and let it exit out of it's main method by itself. Changing the value of a volatile variable that the thread is polling, is one way of doint that.
ofeririko wrote: I wanted to implicity shut down the internal Thread so I tried to implement Finalizer. this didnt work for me - the Internal thread kept running and the Finalizer never called
Of course not, the Finalizer is only called once the garbage collector notices that the object is up for garbage collection, but as the thread is referencing the object, it never will be.
If you want to control the life cycle of an object, you should implement the IDisposable interface.
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
hi friends
i have a question about object oriented(class inheritance)
i have a windows application with c# that in this application i have 2 forms. these 2 forms have few methods i show you below.
========> form1
public partial class form1:Form
{
public form1()
{
InitializeComponent();
}
public void change_value_label(string new_value)
{
lbl.Text=new_value;//this label defined as private controll for this form
}
}
=========>form2
public partial class form2:Form
{
public form2()
{
InitializeComponent();
}
private void subject_Load(object sender, EventArgs e)
{
//in this area code i want to write a code that call change_value_label method of form1 , but i can't
// if i create a new object of form1 then i can call the method but with this way i cannot change the value of the label on form1
//and if i declare change_value_label method on form1 as static method then on the method i cannot access to the label because this controll is not static and i //cannot define the label as static control
//please tell me what do i have to do to solve this problem?
}
}
form1 and form2 are showing at te same time because this two forms are children forms.
thank u.
nobody help you...
you have to help you yourself
and this is success way.
|
|
|
|
|
I'm not sure what this has to do with inheritance - both forms are inheriting from System.Windows.Forms.Form
Anyway, I answered a similar question a few minutes ago here[^].
If both forms are child forms then you may need to use events as well.
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
|
|
|
|
|
Colin[^] has a good article on his blog here[^]
DaveBTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
|
|
|
|
|
Add a handler for the load event of form2 in form1 and do whatever you need to do. This is the easiest solution and it is OO as well.
To do so, create a method or property in form1 and send it the instance of form2. Then within form2 create an event handler for the load event of form1 and do whatever you need to--change the label.
|
|
|
|
|
I am attempting to modify a file that a program has a lock on which is write-only. Is there some way i can do this in C#?
Einstein argued that there must be simplified explanations of nature, because God is not capricious or arbitrary. No such faith comforts the software engineer.
-Fred Brooks
|
|
|
|
|
StevenWalsh wrote: Is there some way i can do this in C#?
There shouldn't be. Other programs usually have locks on files for a reason.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Hello
I'm trying to open the print dialog using the following code, tryin to set the selected printer to "PDF995" instead the default one
But it always shows the default
However I can manualy select "PDF995"
What am I doing wrong ?
Thans for any help
PrintDialog pd = new PrintDialog();
pd.PrinterSettings.PrinterName = "PDF995";
if (pd.PrinterSettings.IsValid)
{
int a = 1;
}
pd.Document = printDoc;
printDoc.DefaultPageSettings.Margins = printmargins;
pd.AllowCurrentPage = true;
pd.AllowSelection = true;
pd.AllowSomePages = true;
pd.AllowPrintToFile = false;
if (DialogResult.OK == pd.ShowDialog())
{
SetupPrint(pd);
printDoc.Print();
}
|
|
|
|
|
I need to create PDF documents on the fly. I came across libraries such as iTextSharp, PDFSharp, PDFClown etc. Which one is better? Can anyone recommend one? I am using .Net 2.0.
|
|
|
|
|
CodingYoshi wrote: Which one is better? Can anyone recommend one?
Only you can choose the one that is the best for you. This is a highly subjective issue, and it's up to you to look at it based on the criteria that you think is important - for instance, is ease of use important to you, or support for the latest versions of the PDF format, or speed of PDF creation? Only you can decide which meets your criteria.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
