My guess is the limit clause is doing something odd. Try limiting using LIMIT 10 OFFSET 0 if you need a limit (that was a guess from the LIMIT man page - I'm not that familiar with progresql)
HTH Rob. On Thu, 6 Jan 2005 12:22:20 +1100 (EST), [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Here is the SQL: > > select claimspaym0_.id as id, claimspaym0_.member_id as member_id, > claimspaym0_.policy_id as policy_id, claimspaym0_.entry_date as > entry_date, claimspaym0_.family_name as family_n5_, claimspaym0_.status as > status, claimspaym0_.amount as amount, claimspaym0_.coverage as coverage > from claims_payments claimspaym0_ where (claimspaym0_.status>='en' ) order > by claimspaym0_.status limit ? > > For one DB on a debian server with postgres 7.4.6 this returns no rows. > > For another DB on a mandrake laptop with postgres 7.4.1 this returns the > correct 10 rows.... > > Is it something I said or is there a CREATEDB switch or something? Anyone > know? > > HNY one and all. > > Stuart > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > -- Rob Sharp e: [EMAIL PROTECTED] w: quannum.co.uk j: [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
