relying on the assumption that the transaction will be remembered. As an example, a bank
banking application might wish to check that the sum of all credits in one table equals the sum of debits in another table, when both tables are being actively updated. Comparing the results
bank balances with transactions like: BEGIN; UPDATE accounts SET balance = balance + 100.00 WHERE acctnum = 12345; UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 7534; COMMIT; If two such transactions concurrently try to change the balance
rely on configuration files, such as files of stop words. These files must be stored in UTF-8 encoding. They will be translated to the actual database encoding, if that is different, when they
bank SET balance = balance - debit WHERE accountno = tp1.accountno RETURNING balance; $$ LANGUAGE SQL; To call this procedure, an argument matching the OUT parameter must be included. It's customary to write NULL : CALL
bank SET balance = balance - debit WHERE accountno = tf1.accountno RETURNING balance; $$ LANGUAGE SQL; If the final SELECT or RETURNING clause in a SQL function does not return exactly the function's declared result type, PostgreSQL
bank SET balance = balance - debit WHERE accountno = tf1.accountno RETURNING balance; $$ LANGUAGE SQL; A SQL function must return exactly its declared result type. This may require inserting an explicit cast. For example, suppose we wanted
bank SET balance = balance - debit WHERE accountno = tf1.accountno RETURNING balance; $$ LANGUAGE SQL; 35.4.3. SQL Functions on Composite Types When writing functions with arguments of composite types, we must not only specify which argument
bank SET balance = balance - debit WHERE accountno = tf1.accountno RETURNING balance; $$ LANGUAGE SQL; 37.4.3. SQL Functions on Composite Types When writing functions with arguments of composite types, we must not only specify which argument
Соглашаюсь с условиями обработки персональных данных
