(journalism) A line at the beginning of a document (such as a newspaper article) stating the place of origin and typically the date, and often written in capital letters.
dateline m (plural datelines, diminutive datelinetje n)
(journalism) dateline....
Verb: dateline (third-person singular simple present datelines, present participle datelining, simple past and past participle datelined)
@MaxVernon Fun (?) trivia. the woggy parent axis in the answer by Mr. Rutzky is not a problem with the new cardinality operator but with the old one it is horrible. The use of parent axis in answer by @sp_BlitzErik is not a problem with either cardinality estimator. "Woggy" pretty much sums it up.
Don't know about others but for me it's clearer without the #. Otherwise I might think that the # was part of the command. I've seen the # used in other posts, though. But then there would always be a space between the # and the subsequent command.
(At least I think it was always so.)
On a different note, it's too bad that neither the person who suggested the edit nor the one who "improved" it took care of other things, like capitalising the first word of each sentence or replacing that pesky "u".
Yes, I understand that the space is part of the prompt. My guess is that it is usually there by default*, hence examples of command lines that do have the delimiting space may be prevalent. *I also realise that might depend on the specific distro/version used.
@ypercubeᵀᴹ On the other hand, if no-one does, the question effectively stays unresolved, draws attention, then someone sees the comment, realises, "Oh, there's already a solution, I shouldn't bother", rinse, repeat
(Actually please do post these answers. Although it is not my question I will probably refer back to it in future, despite the annoying use of keywords as coumn and table names.)
@dezso That should be an answer as it is the only answer — either that or we close the question, but I can see it having some value with your answer attached
Looks like this was meant to be a comment in another answer (and rep=1 does not allow comments on others posts). Your other answer seems fine (not sure if it's correct but looks like it) — ypercubeᵀᴹ39 mins ago
I'm not entirely sure but it looks like his two answers could be merged into one
The one that looks like a comment appears to be explaining the reason for the problem happening. If that is so, it would be perfectly fine as part of the actual answer.
I'd combine them straight away, I'm just not sure if my understanding of that "answer comment" is correct.
@AndriyM Yeah, it might be good as part of his other answer. When I read it, it looked like a reply to either the accepted answer or to Rick's comment.
I'm guessing the files were initially exported in UTF-8. Exporting in ASCII could well work for them. E.g. "Ligações" can be saved in Win-1252 without data loss
@PaulWhite that animation really should go. It's totally distracting and doesn't add anything to the answer, even if it was a little funny. We definitely don't stand for any fun around here.
@AndriyM yes, I was thinking initially of adding some code to show various ways to add ranking. Now, I think Lucy should ask a new question if they still want ranking.
There is a reason why the UPSERT syntax and functionality was added to Postgres. I wouldn't go into much detail, because it's described exhaustively elsewhere, but the most issues with upsert stem from concurrency. INSERT ... ON CONFLICT UPDATE ... solves these issues and gives you, in the end,...
@ypercubeᵀᴹ The inconsistency of the entity names in their column names is a problem. It's something that would need to be addressed in the answer IMHO
They also have Client_Web_Address which they don't want to match when looking just for Address
No, int[] just means an array of int. The number of items is determined from the interpretation of the literal preceding the type. The literal is NULL, meaning the array is empty.
@dezso Complicating matters is much more fun. You'll never get any functionality out of your application, which is good for job certainty. — Gerard H. Pille2 hours ago
flagged this already, to me it is a clear violation of 'be nice'
I wouldn't say it's not nice, but I think I may at this point have formed some opinion of him. I think he's just being a little sarcastic. Messing around. Having fun (which is prohibited on SE, of course).
@dezso I don't know if my edit truly reflects your meaning. It seems to make slightly more sense to me in that context but please let me know if I got it wrong
I need to know is it possible to convert utf8 special characters to ANSI in an SQL file without changing the encoding of the file, and if yes, how?
I have the character È and I need to write a query with it in an ANSI file, but I am not allowed to change the encoding of the file. Every time I pas...
Maybe this is a good or a bad question but in my Google research I wasn't able to find out a good answer (maybe because I sucks performing a good search). In a few words:
can a DB be created without a user and/or owner?
I am trying to answer a question in SO and the user share it DB configura...
It's unlikely at this point of the career for most of these guys. We'll see. Luckily the Wolves look to be improving significantly year over year so I won't be out of sports for the winter lol
@AndriyM not bad. When I worded that, I was also thinking about the versions that don't yet have the proper upsert - there all upsert implementations suffer from this :D
@Lamak Obviously. Coincidence, I received a mail today, that the airbag must be replaced because it's faulty.
> In the event of driver’s airbag deployment the internal pressure of inflator may increase abnormally and in an extreme case cause the driver’s airbag inflator casing to rupture. In an extreme case this may cause a scattering of metal fragments.
"Nothing to worry about, you have only be driving a car with a potentially killing airbag for 10 years" ;)
@dezso Do you mean versions that already supported the upsert syntax but the implementation was buggy? I guess calling those implementations "custom" would be unfair. I'll see if I can think of something else
@dezso Oh I see, it's what I thought from the beginning. In that case I think "custom implementation" would apply to any attempts at upsert in those versions.
@ypercubeᵀᴹ I noticed it in the original question before I removed the other tags. I removed the other tags since the question only makes sense for a single DBMS at a time. If the question is really about any DBMS, then the question cannot be conclusively answered, and should just be closed. IMO.
I was going to VtC that question, but with 2600+ views, it's clearly going to help some people to have it answered. Should I re-flag those remaining comments? or should they stay?
@McNets - answers should be answers, not comments...
Have you tried to enclose the path between ". copy d:\bla "\\p1\p2\p 3.xls"? — McNets1 hour ago
still in flight. getting closer. we should be getting our travel notification within the next 4-6 weeks which means we'll be in s. korea in july. considering just living there for a few weeks until we get approval for him to come back to the us