On Nov 12, 2010, at 7:20 AM, Roger Binns wrote:
A ticket that has been open on this topic since January 2006.
Oops, forgot to paste:
http://www.sqlite.org/src/tktview?name=23b2128201
Thanks for that. Since 2006? High priority indeed :)
That said, maybe SQLite has reached a point where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2010 10:04 AM, Petite Abeille wrote:
Thanks for that. Since 2006? High priority indeed :)
That the ticket averages a small number of comments per year is an
indication that perhaps its priority is about right. Many other ticket
tracking
On Nov 12, 2010, at 8:18 PM, Roger Binns wrote:
Your definition of proper appears to be some ISO standard :-)
Nah, not specially fond of that ISO standard, more for illustration purpose
really.
SQLite's approach is certainly acceptable to most (evidence: if not
there would be a lot of
Hello,
Is there a way, short of parsing the original DDL, to retrieve a constraint
name?
For example, given:
create table foo
(
bar text,
constraint foo_uk unique( bar )
)
How does one retrieve the unique constraint name, foo_uk?
Thanks.
Cheers,
PA.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2010 11:12 AM, Petite Abeille wrote:
Is there a way, short of parsing the original DDL, to retrieve a constraint
name?
[..]
How does one retrieve the unique constraint name, foo_uk?
A ticket that has been open on this topic since January
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2010 09:40 PM, Roger Binns wrote:
A ticket that has been open on this topic since January 2006.
Oops, forgot to paste:
http://www.sqlite.org/src/tktview?name=23b2128201
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10
