-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Bayer ha scritto:
> On Feb 28, 2010, at 3:21 PM, Manlio Perillo wrote:
> 
> When reading the code in the `sql.compiler` module, I noted this:
> 
>    def visit_drop_table(self, drop):
>        ret = "\nDROP TABLE " + self.preparer.format_table(drop.element)
>        if drop.cascade:
>            ret += " CASCADE CONSTRAINTS"
>        return ret
> 
> The problem is that this syntax is not supported by all backends!
> I have checked the SQL 2003 standard (a draft), and it seems that
> "CASCADE CONSTRAINTS" is *not* standard.
> 
> 
>> that was proof of concept only.  removed in r6884.
> 

Why?

I think it is fine.


Manlio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuLE70ACgkQscQJ24LbaUSszwCgglzVSnb12atzAwi2UDdtVoPn
jt4AniOVDjwwBNDmGFFBw+a/mJynX7dY
=Wjhp
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to 
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.

Reply via email to