Sefan Heymann wrote:
> I think in PSQL the semi-colon is there to terminate a statement, and
> it is also required to be there (except after END).
Because END is not a statement.
> begin
> One;
> Two-- syntax error in PSQL
> end;
The semicolon after 'end' is also a syntax error
On 21-11-2014 18:46, Stefan Heymann wrote:
>>> "All statements except the BEGIN…END blocks must be separated by a
>>> semicolon.."
>>> - terminated, not separated.
>>
>> I think separated is actually correct here (although terminated is as
>> well). The statement is terminated by the semi-colon, b
On 21-11-2014 18:41, Paul Vinkenoog wrote:
> Mark Rotteveel wrote:
>
>>> "All statements except the BEGIN…END blocks must be separated by a
>>> semicolon.."
>>> - terminated, not separated.
>>
>> I think separated is actually correct here (although terminated is as
>> well). The statement is termi
>> "All statements except the BEGIN…END blocks must be separated by a
>> semicolon.."
>> - terminated, not separated.
>
> I think separated is actually correct here (although terminated is as
> well). The statement is terminated by the semi-colon, but multiple
> statements are separated by the s
Mark Rotteveel wrote:
> > "All statements except the BEGIN
END blocks must be separated by a
> > semicolon.."
> > - terminated, not separated.
>
> I think separated is actually correct here (although terminated is as
> well). The statement is terminated by the semi-colon, but multiple
> statement
On 21-11-2014 09:18, Helen Borrie wrote:
> "Each block of statements must be put within the statement parentheses BEGIN
> and END."
>
> Statement parentheses? BEGIN and END are block delimiters.
> If the whole of their work is like this, the result would need some pretty
> close editing before b
Hello Alexey,
> >I think this proves my point that the translation should be done by a
> native English speaker.
>
> If you know someone, please give me his contacts.
I already recommended proz.com. This is probably the best site in the world
for finding qualified translators and information on t
> So, text should look like this:
> Each block of statements must be put within the operator parentheses
> BEGIN and END
>
> Not very good? Fine, then something like this:
> "Each block of statements must be put within block delimiters BEGIN and
> END."
I think the original text se
Paul,
>I think this proves my point that the translation should be done by a
native English speaker.
If you know someone, please give me his contacts.
>Of course we can't expect a translator to know all about
>SQL terminology, but if you don't know what parentheses are, you're
not fit to d
Alexey wrote:
> In the original Russian text there is a term which is directly
> translated as "operator parentheses", which is commonly used in Russia
> (and, as "operator parentheses", exists as English term).
(...)
> So, text should look like this:
> Each block of statements must be put withi
Hi,
I am far from the hope that text after translation will be immediately
ready for publication, definitely it will require proof-reading (and
here additional funding will be good too).
However, we need to manage our expectations, let me explain using
Helen's comments as example:
>Statem
At 08:17 p.m. 21/11/2014, Alexey Kovyazin wrote:
>Hi All,
>
>I have submitted your feedback to translators, and they provided new version
>https://yadi.sk/i/vavPQbm7cqjK6
>
>Please review it and let's decide - should we give these guys a chance
>or need to turn to another?
It's really hard to say
12 matches
Mail list logo
