Re: [SQL] Update and trigger

Thanks...but a difference seems to be that the rule is not specific to update on a particular col but any col of a row getting updated... Thanks On Tue, Jun 10, 2008 at 10:21 PM, A. Kretschmer < [EMAIL PROTECTED]> wrote: > am Tue, dem 10.06.2008, um 18:45:51 -0700 mailte Medi

[SQL] Update and trigger

Hi, I need to increament a counter such as myTable.Counter of type integer everytime myTable.status a boolean column is updated. Can you help me complete this... create trigger counter_trigger after update on myTable.counter execute procedure 'BEGIN statement; statement; statement END' Q1- how d

Re: [SQL] Conceptual Design Question

Assuming common semantics for a given field then the question of breaking it to many parts is also a function of its size as related to I/O. We know that memory allocation and I/O read/writes are not granular to bytes and are rather blocks of bytes as it travels from VM (virtual memory) all the wa

Re: [SQL] Query question

Thanks Stephan, My real DDL include a forign key reference to T2.id and since I am ok with NULL value then the "left outer join" indeed have solved the problem. Thanks again Medi On Thu, May 22, 2008 at 2:50 PM, Stephan Szabo <[EMAIL PROTECTED]> wrote: > On Thu, 22 May 2

[SQL] Query question

Hi, I can use some help with the following query please. Given a couple of tables I want to do a JOIN like operation. Except that one of the columns might be null. create table T1 ( id serial, name varchar(20) ); create table T2 ( id serial, name varchar(20) ); create table T1_T2 ( id serial, t1_

Re: [SQL] Data layer migration from MSSQL

I think the grammer should help the parser to determine what you mean when the token ORDER is seen. for example in a select statement... Syntax: SELECT expression [, ...] ... [ FROM from_item [, ...] ] [ WHERE condition ] ... [ ORDER BY expression [ ASC | DESC | USING operator

Re: [SQL] accounting schema

orries you about bank accounts... Thanks guys...this is very very nice Medi On Feb 6, 2008 6:35 PM, Steve Midgley <[EMAIL PROTECTED]> wrote: > At 05:09 PM 2/6/2008, [EMAIL PROTECTED] wrote: > >Date: Wed, 6 Feb 2008 17:08:54 -0800 > >From: "Medi Montaseri" &

[SQL] accounting schema

Hi, I am learning my way into Accounting and was wondering how Accounting applications are designed. perhaps you could point the way On one hand, accountants talk about a sacret equation A = L + OE (Asset = Libility + Owner Equity) and then under each categories there are one or many account.

Re: [SQL] UTF8 encoding and non-text data types

is the first accurance of semi-colon as in 䕱 which is being caught by PG parser. Medi On Jan 14, 2008 12:18 PM, Steve Midgley <[EMAIL PROTECTED]> wrote: > > On Jan 13, 2008 8:51 PM, Steve Midgley <[EMAIL PROTECTED]> wrote: > At 02:22 PM 1/13/2008, [EMAIL PROTECTED] wrote:

Re: [SQL] UTF8 encoding and non-text data types

CTED] wrote: > >Date: Sat, 12 Jan 2008 14:21:00 -0800 > >From: "Medi Montaseri" <[EMAIL PROTECTED]> > >To: pgsql-sql@postgresql.org > >Subject: UTF8 encoding and non-text data types > >Message-ID: > ><[EMAIL PROTECTED]> > > > >I un

[SQL] UTF8 encoding and non-text data types

I understand PG supports UTF-8 encoding and I have sucessfully inserted Unicode text into columns. I was wondering about other data types such as numbers, decimal, dates That is, say I have a table t1 with create table t1 { name text, cost decimal } I can insert UTF8 text datatype into this table