any attempt to hide information comes with huge fines, jail terms and delisting as possible outcomes. there is a reason companies are afraid to fuck with SEC, and there is a reason they will say things in disclosure statements they would NEVER say publicly. just look at SCO they actually listed their lawsuit failing as a possible outcome in one filing.
no they still must keep an audit able record of their disclosures. this plus the fact once you put it on the net somewhere it's cached they would be screwed
Ok your argument makes sense that the DB could change something and it'd be invisible to the programmers, and impossible for them to work around but that comes down to common communication, and if things were that bad this would be the LEAST of your worries;)
i'm certainly not advocating patch culture either, but it's invenitable that you'll need to. in the case of most places i've worked you have a centralized database which is far easier to update than all the clients
Oh i'm well aware it isn't popular in the real world, because it usually cuts developers grass.
it's better in the following ways:
1. more readable code, there is less of it
2. easier to maintain - change in the database and the change happens realtime, no need to a new release (if your doing binaries)
3. better access control in many situations. sometimes you want to get at data but don't want the users to have that kind of access. you can run a function as a higher level user but allow lower level users select access to the function.
4. faster/more accurate. in general, your DBA will write a better/faster query than your programmers.
5. One less thing for your programmers to worry about. it means they can focus on writing the application (which is their job remember).
I've had people fight me tooth and nail on this before but they always end up coming around. a lot of the time it's also about job security - people worry taking a task off their hands threatens their jobs.
no. have your DBA/database guy write a function to return the datasets you need and use THAT to make the report. I understand some shops can't afford to have both and in that case you must work with what you got, but SQL in the code is bad bad bad.
this is one reason i've always been critical of OSS and it's lack of a real report developing environment like reporting services.
all your apps should only be able to access the DB as unprivileged users with resource limits to prevent crashing, and they should only be able to run stored functions which someone qualified at sql creates for the application guys.
this way the programmers are prevented from infecting the database from their crapness
.... if they GIVE the computers to them you tards. and since when the hell is there an expectation of privacy on a PUBLIC computer???? honestly the stories on/. are getting worse by the minute.
i don't know how, but this is definitely MS's fault. those sneaky pricks at MS have found a way to force apple into using their patented security model.
his last name is libshitz, it's not really THAT obvious that it contains shit in the name. he wasn't some 15yo trying to take the piss, and frankly i'm astounded this went past a 1st level manager.
the fact that you are trying to defend this makes me think your partly retarded so i'll go easy on your downie ass.
i'm struggling to see the point of this, you can build a linux box on cheaper things than a ps3 and this is nothing to do with developing FOR the ps3, it's just a howto install guide
well atleast they have given up pretending to be the good guys. now they don't even need to SUSPECT you've done anything wrong. what the hell kind of criteria do they use if suspicion isn't even needed? do they throw on "frisk the asian guy" days or something just to make it fun?
one thing is for sure, the DHS office will have one hell of a porn collection....
"It is established FACT that Hydrogen is very difficult to contain. It leaks through the tightest seals like they were swiss cheese, and once free it races into the atmosphere and escapes into space."
If what these people said was true i'd be up to my neck in melted polar caps, driving my solar PV powered car and sleeping in my bio dome to escape the mutated nuclear vampire bats at night.
any attempt to hide information comes with huge fines, jail terms and delisting as possible outcomes. there is a reason companies are afraid to fuck with SEC, and there is a reason they will say things in disclosure statements they would NEVER say publicly. just look at SCO they actually listed their lawsuit failing as a possible outcome in one filing.
no they still must keep an audit able record of their disclosures. this plus the fact once you put it on the net somewhere it's cached they would be screwed
i'm certainly not advocating patch culture either, but it's invenitable that you'll need to. in the case of most places i've worked you have a centralized database which is far easier to update than all the clients
it's better in the following ways:
1. more readable code, there is less of it
2. easier to maintain - change in the database and the change happens realtime, no need to a new release (if your doing binaries)
3. better access control in many situations. sometimes you want to get at data but don't want the users to have that kind of access. you can run a function as a higher level user but allow lower level users select access to the function.
4. faster/more accurate. in general, your DBA will write a better/faster query than your programmers.
5. One less thing for your programmers to worry about. it means they can focus on writing the application (which is their job remember).
I've had people fight me tooth and nail on this before but they always end up coming around. a lot of the time it's also about job security - people worry taking a task off their hands threatens their jobs.
this is one reason i've always been critical of OSS and it's lack of a real report developing environment like reporting services.
this way the programmers are prevented from infecting the database from their crapness
.... if they GIVE the computers to them you tards. and since when the hell is there an expectation of privacy on a PUBLIC computer???? honestly the stories on /. are getting worse by the minute.
as apposed to an exploit (which apple ignores or doesn't look into) turning into the equivalent of the code red worm? brilliant PR work there son.
i don't know how, but this is definitely MS's fault. those sneaky pricks at MS have found a way to force apple into using their patented security model.
the fact that you are trying to defend this makes me think your partly retarded so i'll go easy on your downie ass.
"bad words"? what are you fucking 5 years old? this whole thing is insane and anyone who defends it needs to be quarantined and watched closely.
it doesn't matter if it lives. even returning dead proof of life from another planet would be a revelation.
actually they already know other planets in our solar system have been warming. i guess we must still be responsible in some way.
we'll do more than not use it, we will continue to point out how such a retarded policy is wrong, and that's it's costing apple customers.
clearly this is the white man's fault for showing them the pleasures of the internet, then failing to give it to them for free.
i'm struggling to see the point of this, you can build a linux box on cheaper things than a ps3 and this is nothing to do with developing FOR the ps3, it's just a howto install guide
one thing is for sure, the DHS office will have one hell of a porn collection....
this is just another excuse for linux zealots to bash MS
you fail to.
it's definately a crime to think some kid could die in iraq without ever having had a beer.
you fail.
If what these people said was true i'd be up to my neck in melted polar caps, driving my solar PV powered car and sleeping in my bio dome to escape the mutated nuclear vampire bats at night.
their called democrats
I want a gbay. screw ebay and their horrid website layout and policy's.
I hope you are taking the piss.....