Did you do db.commit() after the db.table.drop()?
On Tuesday, 8 January 2013 20:14:23 UTC-6, Liang wrote:
>
> No error shown in the interactive shell after executing the command. But
> the tables in the database are still there. I use Postgresql 9.2.
>
> On Wed, Jan 9, 2013 at 1:35 AM, Massimo Di Pierro
> <massimo....@gmail.com<javascript:>
> > wrote:
>
>> What do you get? An error? What error?
>>
>>
>> On Friday, January 4, 2013 3:18:32 AM UTC-6, Liang wrote:
>>>
>>> drop('cascade') seems not working.
>>>
>>> On Wednesday, 4 February 2009 14:17:14 UTC+8, mdipierro wrote:
>>>>
>>>> give this a try. In trunk
>>>>
>>>> db.table.drop('cascade')
>>>>
>>>> On Feb 3, 11:40 pm, Baron <richar...@gmail.com> wrote:
>>>> > thanks Massimo.
>>>> >
>>>> > On Feb 4, 3:28 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>>>> >
>>>> > > sorry, for now you have to do it manually
>>>> >
>>>> > > db.executesql('DROP TABLE tablename CASCADE;')
>>>> >
>>>> > > perhaps I can add an option to drop/truncate.
>>>> >
>>>> > > Massimo
>>>> >
>>>> > > On Feb 3, 9:01 pm, Baron <richar...@gmail.com> wrote:
>>>> >
>>>> > > > When I try to drop or truncate a table I get this error:
>>>> >
>>>> > > > ProgrammingError: cannot drop table dump because other objects
>>>> depend
>>>> > > > on it
>>>> > > > HINT: Use DROP ... CASCADE to drop the dependent objects too.
>>>> >
>>>> > > > Deleting from the table works fine because the deletions cascade.
>>>> Is
>>>> > > > there a way to truncate or drop tables through the DAL that have
>>>> > > > foreign key dependencies?
>>>> >
>>>> > > > Baron
>>>
>>> --
>>
>>
>>
>>
>
>
--
