Hi Justin,
Here's the schema of my test table:
Table "members"
Attribute | Type | Modifier
-------------+-----------+----------
memberid | integer | not null
firstname | varchar() |
lastname | varchar() |
email | text |
optin | boolean |
timeofvisit | timestamp |
Indices: members_memberid_key,
members_pkey
Since I asked the question, I've found the position of the field in the query appears
to be the issue. If I put the boolean or timestamp field in the last position in the
query, it
locks the CPU. If I put them in the first two positions, it works. Here's it working:
http://frankhilliard.com/~capo/test3.cfm
Here's it not working:
http://frankhilliard.com/~capo/test4.cfm
Here's a picture of what the CPU is doing:
http://frankhilliard.com/lockup.jpg
Here are the actual queries, Test3 which works:
SELECT timeofvisit, editedwhen, noautomail, paid2001, userid, firstname, lastname
FROM members
WHERE userid = 338
Test 4 which locks up:
SELECT noautomail, paid2001, userid, firstname, lastname, timeofvisit, editedwhen
FROM members
WHERE userid = 338
Justin Buist wrote:
> I've used PG and CF together just fine with timestamps. What's the actual
> table schema look like as output from psql using the \d <table name here>
> command?
>
Any suggestions are appreciated.
Frank Hilliard
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
