To achieve a higher level of SQL compliancy..
On Tue, 2004-01-20 at 10:24, Kenneth Gonsalves wrote:
> On Tuesday 20 January 2004 19:26, Chris Bowlby wrote:
> > Hi Ken,
> >
> > Under 7.3.x this option was removed, you need to test via:
> >
> > SELECT * from t
ike so:
> 'select * from table where field = null'
> would give all the rows where that field had no value.
> on porting to 7.3.2, this doesnt work. How to do this?
--
Chris Bowlby <[EMAIL PROTECTED]>
Hub.Org Networking Services
---(end of broadcast)
Ack, I knew it was something small, I was under the impression that I
had been using that, it just took someone to point it out to make me
look again :>... thanks..
On Thu, 2004-01-15 at 14:47, Joe Conway wrote:
> Chris Bowlby wrote:
> > select get_account_info('test.com')
; line 15 at for over execute statement
Jan 15 13:42:56 jupiter 5439[3164]: [134-1] ERROR: set-valued function
called in context that cannot accept a set
Jan 15 13:42:56 jupiter 5439[3164]: [134-2] CONTEXT: PL/pgSQL function
"get_account_info" line 20 at return next
Can anyone see anything that I missed? Or has any suggestions?
--
Chris Bowlby <[EMAIL PROTECTED]>
Hub.Org Networking Services
---(end of broadcast)---
TIP 8: explain analyze is your friend
Hi Marc,
I was actually leaning towards schema's as a method to partition the data
out when I was beginning to plan AMS 2, your suggestions of schema's
confirmed this as a good approach for what we were looking for so I started
to code the initial layout for the Schema in April/May, but at the
