Once saw a new years resolution to "finish more projects than I start" :)
____________________________________________________________ Be brave little warrior, be VERY brave
Once saw a new years resolution to "finish more projects than I start" :)
____________________________________________________________ Be brave little warrior, be VERY brave
I've heard rumors that the Android OS gives less accurate GPS positioning data to non-Google apps (allegedly Garmin comments), I don't think I believe the rumors but Google is getting more and more hostile / aggressive so I wouldn't be surprised if it was true. Personally I don't use Google for anything other than searching...
____________________________________________________________ Be brave little warrior, be VERY brave
I would like to suggest that it is not data wither but noise :)
____________________________________________________________ Be brave little warrior, be VERY brave
Web is supposed to be the platform of preference, and the latest version is supposed to be updated to current requirements, but I still have to jump through hoops to get basic things like number formatting and handling... I don't get it Maybe I shouldn't expect things like localisation to work, even though it works in XAML with virtually no effort. I bind a decimal value to a read only field, when I want to parse it back to a decimal it fails because I have a . instead of a , - ARGH
____________________________________________________________ Be brave little warrior, be VERY brave
"Best practice" or "Common pattern", people tend to confuse the 2... Best practice will have justification(s), common pattern probably won't. Best practice is best for specific reasons / conditions, and those will tell you if it applies to you. Try to get the detail of the best practice and you are likely to find out that it is more common pattern. Something like this sounds more like common pattern than best practice, but I still don't see the advantage / point of doing it. IT people (including me) tend to over complicate things, this sounds like one of those.
____________________________________________________________ Be brave little warrior, be VERY brave
I think you are right but hope you are wrong :) The key to SOA is to implement throughout the vertical, if all is not in SOA becomes an inhibitor and a PAIN.
____________________________________________________________ Be brave little warrior, be VERY brave
I have been coding in SQL for 10+ years, I am very aware of what a stored procedure is.
GuyThiebaut wrote:
Stored procedures in SQL Server use TSQL so just use IF statements within the stored procedure.
Ever seen what happens to performance when an IF statement send processing outside of a pre-compiled execution plan? I don't even know what you mean by saying that a stored procedure uses TSQL, we are comparing sending TSQL strings from an application as code versus calling a stored procedure in the database.
GuyThiebaut wrote:
Calling a stored procedure or running SQL directly via .Net requires a connection the command and parameters - so I can't see what this additional object is that needs managing.
GuyThiebaut wrote:
What's this thing with comparing TSQL and stored procedures(see my response above - a stored procedure can contain TSQL)?
You don't seem to be understanding the question. If you are referring to the code in the stored procedure, I don't understand what you mean by "can contain TSQL", what else can it contain? If you are referring to calling dynamic SQL in a stored procedure, yes I agree, but that is detail we have not discussed and was not asked.
____________________________________________________________ Be brave little warrior, be VERY brave
Yep, I avoid doing Business Logic in a database, also good when using more than 1 DB technology
____________________________________________________________ Be brave little warrior, be VERY brave
This can work the other way... For BI users you want to give read access to tables and now you have to manage security on stored procs as well
____________________________________________________________ Be brave little warrior, be VERY brave
Stored procedures are good when more than 1 operation needs to happen in the database and you can avoid going back to a calling application, that's all I can think of. 1) The do not perform better than parametrised queries, parametrised queries also get compiled and protects against injection 2) They are quite bad with complex IF scenarios (TSQL mostly perform better here), often requiring more than 1 stored proc to be created 3) They are an additional SQL object that needs to be managed 4) Version compatibility matrices can get NASTY with stored procs, with TSQL the application may be able to run on a different version to the database (often not, often true in read scenarios) I used to 'everything in procs', now I do as much as possible in parametrised queries
____________________________________________________________ Be brave little warrior, be VERY brave
Is disagree strongly. Stored procedures should only contain data logic, not business logic. Business logic belongs in the application the business uses, not the database. Your justification for stored procedures as easy way to bug fix horrifies me
____________________________________________________________ Be brave little warrior, be VERY brave
There have been some improvements on the desktop side (just google it), for me performance improvement is huge. If they changed too much (revolutionised) people would have complained, if they didn't (evolution) people would have complained... I think they have built a brilliant long term platform for further evolution.
____________________________________________________________ Be brave little warrior, be VERY brave
Could I suggest that we consider the technical aspects as art as well? A game like tetris is not great in visual stuff, but it's an art to take something that simple and make it as successful as tetris is (dunno how financially successful it is though). The 'user satisfaction' levels of tetris / pacman / etc is also so unexpected I would like to suggest that it is an art.
____________________________________________________________ Be brave little warrior, be VERY brave
I wouldn't admit that I'm working on something that produces that many errors, not publicly or under inquisition...
____________________________________________________________ Be brave little warrior, be VERY brave
My thoughts EXACTLY
____________________________________________________________ Be brave little warrior, be VERY brave
Because people are still looking for a silver-bullet, 1 thing that can do everything for you. Would hate to see the design & architecture of the rest of the 'solution'
____________________________________________________________ Be brave little warrior, be VERY brave
Deny user access?
____________________________________________________________ Be brave little warrior, be VERY brave
That's exactly what happened, irrespective of the condition the code block always executed...
____________________________________________________________ Be brave little warrior, be VERY brave
Happened to me in c++ as a student, nearly gave up programming because of it :)
____________________________________________________________ Be brave little warrior, be VERY brave
I did this once in c++, took very long to figure out:
if (condition);
{
}
____________________________________________________________ Be brave little warrior, be VERY brave