-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 16 Nov 2007 15:25:30 -0500 Tom Hart <tomhart@xxxxxxxxxxx> wrote: > Ok, that makes sense. Like I said I created this db to mimic our > previous db, but I think the best solution here would be to continue > my trend of using all lowercase column names so that I'm not faced > with this problem. > > Thank you for your reply, and you too Joshua. Sorry for such an easy > question :-) No sweat :)... I trust you will have more. Bring them on. Joshua D. Drake > > Sam > > > > ---------------------------(end of > > broadcast)--------------------------- TIP 6: explain analyze is > > your friend > > > ---------------------------(end of > broadcast)--------------------------- TIP 1: if posting/reading > through Usenet, please send an appropriate subscribe-nomail command > to majordomo@xxxxxxxxxxxxxx so that your message can get through to > the mailing list cleanly > - -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240 PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHPf4WATb/zqfZUUQRAntLAJ4s6L7sLvYkeMkwGPfaKu/GuK+gGgCfXXd5 0/qLZJQUZd3TMEk6/vptgls= =uYbF -----END PGP SIGNATURE----- ---------------------------(end of broadcast)---------------------------TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match