Skip Menu |
 

This queue is for tickets about the SQL-Translator CPAN distribution.

Report information
The Basics
Id: 83092
Status: open
Priority: 0/
Queue: SQL-Translator

People
Owner: Nobody in particular
Requestors: thaljef [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.11016
Fixed in: (no value)



Subject: Add support for COLLATE constraints for SQLite
Download (untitled) / with headers
text/plain 162b
The SQL Fairy doesn't seem to know about COLLATE for SQLite. I'm going to attempt to add it. But if my head explodes, this bug report will be here for posterity.
Download (untitled) / with headers
text/plain 607b
This looks like a rathole (for me, at least). I was able to add COLLATE to the grammar and parse it fairly easily. The problem was figuring out how to wedge that in the internal data model. SQLite expresses COLLATE as a column constraint even though it really isn't. This doesn't line up well with SQL::Translator's understanding of constraints. An alternative might be to express COLLATE as an "extra" attribute which seems to be how SQLT handles non-standard bits of SQL for other dialects. I didn't explore that possibility myself. If you can give me some guidance, I might make another attempt.
Download (untitled) / with headers
text/plain 376b
On Mon Feb 11 23:16:04 2013, THALJEF wrote: Show quoted text
> An alternative might be to express COLLATE as an "extra" attribute which > seems to be how SQLT handles non-standard bits of SQL for other > dialects. I didn't explore that possibility myself.
This is probably workable - the mysql parser/producer roundtrip collation precisely this way - via extra attrs. Please explore further.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.