Re: [HACKERS] Variable substitution in psql backtick expansion
От | Fabien COELHO |
---|---|
Тема | Re: [HACKERS] Variable substitution in psql backtick expansion |
Дата | |
Msg-id | alpine.DEB.2.20.1704111558030.29476@lancre обсуждение исходный текст |
Ответ на | Re: [HACKERS] Variable substitution in psql backtick expansion (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: [HACKERS] Variable substitution in psql backtick expansion
|
Список | pgsql-hackers |
> I think so implementation of simple expression evaluation should not be > hard Indeed it is not hard, it is rather a matter of deciding what it should do, and the syntax to do it. > - really just - we can expect so any variable will be replaced by > const in expression > > Num (<|>|=|<=|>=) Num <> and != would seem handy as well. > Text (<|>|=|<=|>=) Text What would be the use case for handling TEXT? > not Bool, Bool (or|and) Bool Aka logical expressions. > and special operator "defined" I'm still not buying this suggestion at all because it does not look like SQL and I think that client-side expressions should be a simple subset of SQL expressions, which a "defined" operators is definitely not. >> Hmmm. I'm not sure I get it. The penalty I see is that it adds a dummy >> variable which must be given a sensible name, and for very short >> expressions this is not a win. But this is a minor point. > I know so it is not ideal - but the language with commands "\if", "\else" > ... is not ideal language. Sure. -- Fabien.
В списке pgsql-hackers по дате отправления: