Click here to Skip to main content
15,896,606 members

Comments by Remi BOURGAREL (Top 9 by date)

Remi BOURGAREL 22-Mar-12 7:12am View    
Reason for my vote of 1
SELECT * is a bad practice because : 1/ you'll have to use your fields by their names anyway 2/ because your DBMS will do additionnal wrk to get all the fields name.

And your solution is really bad because for each request to your table you'll have to query some system table ...

If you got a lot of fields, you can generate a select statement with SSMS.
Remi BOURGAREL 27-Dec-11 5:49am View    
Deleted
ISanti , I'd say that naming a class SomethingInfo is kind of a smell to me, either it's a business object and you name it File or it's a service class and you name it SomethingService. They might should have named it FileLocation, and get rid of this "File" static class.
Remi BOURGAREL 21-Dec-11 3:56am View    
Deleted
Because there is a function Exists() an a function Create() ?
Remi BOURGAREL 12-Apr-11 3:05am View    
Deleted
I'd say : always expect the framework to work as the documentation says not as you think (everyone thinks differently, the documentation is the truth).
Remi BOURGAREL 5-Apr-11 3:24am View    
Deleted
Hmmm no the first solution is for every application, html is client side so I don't see why there is something to do with asp or not.

Vote 1 because anyone knows how to change an attribute with javascript