PostgreSQL, already a mature database, needs to have more options for
recovery as compared to proprietary databases. I just worked with Oracle's
FlashBack query feature in Oracle 9i and FlashBack Table feature in 10g.
Future versions of PostgreSQL must have similar features which enable users
to
that was created three days ago is
not feasible. The changes in other tables and the new things created need to
be done again at the price of just undoing the last update on a particular
table.
Warren Turkal-5 wrote:
On Saturday 17 February 2007 07:49, RPK wrote:
PostgreSQL, already a mature
, as they say), must have an optimized way for undoing of at
least a week changes. A week log is enough and PostgreSQL can keep on
removing old logs automatically.
Secondly, it must be left to the user to decide for the number of days of
archive he want to store. Again upto a week max.
RPK wrote:
I agree
PGSQL and NPGSQL does not display exact error while using with VB.NET. We
faced a lot of trouble to find out actually where an error occured.
For example in a routine we need to insert a record to the table. I forgot
to use values clause in the Insert Query, but PGSQL displayed error No
source
I installed NPGSQL for connectivity with VB.NET but noticed it's performance
slow as compared with ODBC driver. Why?
--
View this message in context:
http://www.nabble.com/NPGSQL-ODBC-performance-tf3293489.html#a9160834
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
SORRY.
--
View this message in context:
http://www.nabble.com/NPGSQL-ODBC-performance-tf3293489.html#a9162156
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
---(end of broadcast)---
TIP 9: In versions below 8.0, the
