I have written a simple web application using pure pl/pgsql and so far it
is working really well (I find it quite easy to maintain as well especially
in terms of form validation).
Basically, apache/php passes receives the incoming web request and calls a
"serve_page" function in postgresql passing
@postgresql.org
>>> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of inspector morse
>>> Sent: Thursday, March 05, 2015 9:21 AM
>>> To: pgsql-general@postgresql.org
>>> Subject: [GENERAL] Sharing data between stored functions?
>>>
>>>
&g
How do I access a cursor's column using a string column?
Example:
CREATE FUNCTION write_html_select(items cursor, data_value_field text,
data_text_field text)
AS
$$
DECLARE r RECORD;
html TEXT;
BEGIN
FOR r in items LOOP
html = "";
END LOOP;
RETURN html;
END;
$$
LA
SQL Server has a feature called Indexed Views that are similiar to
materialized views.
Basically, the Indexed View supports COUNT/SUM aggregate queries. You
create a unique index on the Indexed View and SQL Server automatically
keeps the COUNT/SUM upto date.
Example:
CREATE VIEW ForumTopicCounts
Is there any work being done on materialized views for version 9.7? This
postgresql feature is severely lacking compared to similar features like
indexed views by sql server.
In all other DBMS, the variable names have a distinctive character to
differentiate between variables and column names:
Example:
SQL Server uses @
MySql uses ?
Oracle uses :
Firebirdsql uses :
It makes it easier to write and manage queries especially in stored
procedures.
Just compare the below:
15 04:57 PM, inspector morse wrote:
>
>> In all other DBMS, the variable names have a distinctive character to
>> differentiate between variables and column names:
>>
>> Example:
>> SQL Server uses @
>> MySql uses ?
>> Oracle uses :
>> Firebirdsql
Is it a good idea to write a simple application (consisting of just data
entry interfaces) in pure pgsql?
Basically, we would have each page has a stored function in postgresql that
is called by php+apache (the http get/post values would be passed into
postgrel as an array).
The pgpsql would rend
main concern is, since there will be a lot of concatenation in pgsql to
generate the HTML, would it affect performance?
On Sat, Feb 28, 2015 at 11:08 PM, BladeOfLight16
wrote:
> On Sat, Feb 28, 2015 at 3:39 PM, inspector morse <
> inspectormors...@gmail.com> wrote:
>
>>
>&
