The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
An advanced language for querying databases that doesn't involve tons of ridiculously intricate frameworks and mysterious black box middle-tier software. Preferred by people who break out in a rash anytime something becomes more about the architecture then getting stuff done.
Then we have made no progress in 40 years since SQL was developed, if a 40 year old technology is advanced. You must think that there has also been no significant improvement in software languages in since Fortran 1V.
Then we have made no progress in 40 years since
SQL was developed, if a 40 year old technology is advanced. You must think that
there has also been no significant improvement in software languages in since
That of course has nothing to do with what I said.
Unless of course you think that Fortan or something like C++/C+#/Python exist to solve data storage problems.
Solid advice but the ONLY time I ever use the delete command is to clear test database tables. I never use delete in production - everything is a log and if the user doesn't want to see it anymore a flag is set on the record.
I was getting burned too often by people who would blame me for bad data.
Every item and every change is logged and nothing is ever deleted.
Agreed, solid advice, but cloud storage (my company is in Azure now) makes soft deletes expensive. What we've started doing is setting soft deletes on large blobs, then purging those older than 90 days every month or so; if they don't notice it in 90 days, then YAGNI
If get in the habit of putting all your statements inside a transaction, then if you realize you made a mistake you can roll it back without affecting the table.
Of course, you have to remember to commit the transaction in a timely manner, otherwise the table remains locked.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
I'm not sure, but it may depend on the driver. We use the Jet4 oledb driver for Access and it is quite happy to delete with or without the *. Our apps run can use either SQL Server or Access for the backend, and Delete operations don't require any special handling. (aside from date delimiters) Basically, if it works in Access, it will work in SQL Server, but not always the other way around.
I have been reading about the effect of hurricanes in Cuba. It is unbelievable to think that in this century which is barely a decade old there have been 7 hurricanes with over a billion dollars of damage, the worst being Ike which was 7.3 billion. Considering the impact in the US, this is so much worse. Cuba has a GDP of $57 in 2010. Compared to that the oil rig fire is nothing.
Most of them want to just 'talk-and-bark' on the wire including the confidential and important details but are hesitant to put something in black and white and get it liaised through their SMTP. Is this an indication of their inertia/laziness or some sort of shadowy gesture?
Pretty sure it's because they feel they can "sell" you the job better (and maybe to gauge your response). Also because their understanding of the job changes over time and they can verbally tell you about those changes without having to update the (insanely inaccurate) job description. I suspect your other theories have some merit as well.
Is this an indication of their inertia/laziness or some sort of shadowy gesture?
I am going to suggest an alternate hypothesis ... than those I interpret as implicit in the other replies to your question ... although, I think, all the viewpoints, in the other responses, could be factors in what you apparently experience (which, for me, lacks enough detail for me to really have a strong sense I understand what you are experiencing ... for example: what does "liaised through their SMTP" mean in this context ?).
I'd limit my hypothesis in scope to the contemporary U.S.A., simply because I am not aware of other countries' laws, and the extent to which "danger of litigation" is as "acute" as I believe it is in today's America, which I believe has, correctly, been described as a "highly litigious" society.
So, to bring this down to earth, I'd propose a possible major factor here, if what you experience is within the context of American software recruiting, could be very simple: fear that written responses/documents could be a source of lawsuits, legal harassment, etc.: or, if what the recruiter wrote to you somehow got back to the company they were discussing: it might cause problems for them, perhaps lose them a client ... because the written word can so easily be mis-construed; because someone at their client company might feel they had improperly disclosed confidential company information ?
I'd also propose that there may be some qualitative differences in interaction with recruiters, as you "go up the scale" to higher-paying, senior positions, where you must have a documented, excellent, track-record of real-world achievement, to be even considered ... compared to entry-level positions.
I once had an American friend of mine "screwed" out of 50k US$, because he took on a major project for Apple through their major out-sourcing "buffer company;" the project authorization was signed off-on, in writing, by a senior-level Apple executive. Payment was withheld after a dramatic failure of the software in a major Apple public event; he could have sued: the major-outsourcer for Apple bluntly told him that if he sued, he'd never get a contract with Apple again, because his potential suit might cost Apple "face" (and possibly a senior executive a job ... and he made a vast amount of money sub-contracting for Apple over years). He chose not to sue, and to eat the loss of US $50k. The business he did with Apple, over the next years, more than made up for the loss: it's a dog-eat-dog world out there ?
And, last, but not least, taking the "darkest possible" view, one might consider professional recruiters, who make their money off commissions, and are independent of the companies they recruit for, as being, as a "class," naturally gifted bulls***t artists (a skill absolutely necessary in their "profession" ?).
but are hesitant to put something in black and white and get it liaised through their SMTP. Is this an indication of their inertia/laziness or some sort of shadowy gesture?
Recruiters that are any good are people persons. They make money buy building relationships. And long lasting ones. So they probably like talking more on the phone and face to face.
I would also suspect that they are not detail oriented. Their job probably doesn't require the same level of detail that something like programming does. Thus they need not be precise in communications of any sort.
Just as important the work they do is not black and white either. They might hear on Tuesday from their contact that you are the best interviewee the company has ever seen but then hear back on Wednesday that the company is 'going in a different direction' or 'still looking' or even 'scaling back'. Until they have the contract it isn't set and they deal with that reality every day unlike your that probably only deals with it at most every couple of months. So they tend to keep things indefinite.
Similar to Gmail's Pop service where other email accounts are automatically pulled to Gmail Inbox periodically, shouldn't Google Voice consider implementing a pop feature to aggregate voice messages from T-Mobile, AT&T and our other voice messaging systems?