Keith Pierno writes:
>
>
>
BTW, please do not post all-HTML mail to this list.
> The timeline for the events all dates MM/DD/
>
> 06/09/2009 1310 EDT - Hardware fault on primary database server db01pri
> 06/09/2009 1325 EDT - Failover to warm standby db01sec
Hmm, how exactly was
"David Tandwe" writes:
> I am using postgreSQL with the OLEDB provider but I am failing to update
> data in a database. I reports the error indicated in the subject of this
> message.
I doubt you'll find any help for that here. Try asking on a
PGOLEDB-specific mailing list.
"Jim Michaels" writes:
> Using PGAdminIII and the following query, I get this explain error:
> ERROR: syntax error at or near "DROP"
> LINE 91: DROP TABLE IF EXISTS work;
> ^
If you're not going to show us the previous 90 lines of your script,
we're not really going to be able to help
The timeline for the events all dates MM/DD/
06/09/2009 1310 EDT - Hardware fault on primary database server
db01pri
06/09/2009 1325 EDT - Failover to warm standby db01sec
06/12/2009 1615 EDT - db01pri server fixed and OS booted
06/15/2009 1115 EDT - started recovery of hot
I am using postgreSQL with the OLEDB provider but I am failing to update
data in a database. I reports the error indicated in the subject of this
message.
Is there any solution to this problem?
Please help
David Tandwe
--
Scanned on: ESCOM mailserver
ESCOM
Staus: Clean
Looks like you have a hidden character before DROP. Character 2584 is
called the Lower Half Block, it might be there. Cleanup your code,
make sure there is nothing left and then execute your query again.
Good luck!
Frank
Op 16 jun 2009, om 08:58 heeft Jim Michaels het volgende geschreven:
The following bug has been logged online:
Bug reference: 4855
Logged by: Jim Michaels
Email address: jmich...@yahoo.com
PostgreSQL version: 8.3.7
Operating system: Windows XP Pro Sp3
Description:Explain errors on drop table if exists
Details:
This syntax clearly wor
