|
On 07/20/2012 05:54 PM, Roshan Saxena
wrote:
Yes it is connect and insertion and udation and deletion is taking
place normally but the proble of table drop occurs when I make any
changes in my models in play
Please reply to the mailing list (reply all) not to me directly.
If Play framework is issuing a DROP TABLE, then you need to ask for
help with the Play people. PostgreSQL has no way of knowing that you
don't want the DROP TABLE your framework asks for.
On Thu, Jul 19, 2012 at 9:25 AM, Craig Ringer <ringerc@xxxxxxxxxxxxx>
wrote:
On 07/19/2012 03:19 AM, rajonrole@xxxxxxxxx
wrote:
I am creating one application using play in the models I had
created a table and everything is working fine except when i
make changes in any of the object(fields) all the previous
data in the database is getting dropped how to recover that
If you want to investigate it from the database side, set
log_statement='all' in postgresql.conf, reload or restart
PostgreSQL, and run your test. Now examine the logs and trace
what the framework did. Check to see if:
- It ever connects to PostgreSQL at all. You might be using an
in-memory h2 or derby instance and just think you're using
PostgreSQL
- It ever inserts any data
- It ever commits its transactions
If you confirm that it's getting its data into PostgreSQL, you
then need to look and see if it's deleting it again by checking
the log for DELETE and TRUNCATE statements.
It could also be re-creating your tables every time it runs.
Check for "CREATE TABLE" statements.
--
Craig Ringer
|
