OK, one of the devs on the GitHub page for that FDW helped me realize that I had accidentally mapped the wrong table! Doh!
Deven
On Fri, Mar 27, 2015 at 5:31 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 03/27/2015 02:20 PM, Deven Phillips wrote:
Yes. Here's the MySQL schema:
CREATE TABLE `liquorstore_backendipaddress` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`backend_network_id` int(11) DEFAULT NULL,
`backend_virtual_interface_id` int(11) DEFAULT NULL,
`address` varchar(15) NOT NULL,
`is_gateway` tinyint(1) NOT NULL,
`is_reserved` tinyint(1) NOT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `backend_network_id` (`backend_network_id`,`address`),
KEY `liquorstore_backendipaddress_4a648124` (`backend_network_id`),
KEY `liquorstore_backendipaddress_27235e4d`
(`backend_virtual_interface_id`),
CONSTRAINT `backend_network_id_refs_id_1d869576` FOREIGN KEY
(`backend_network_id`) REFERENCES `liquorstore_backendnetwork` (`id`),
CONSTRAINT `backend_virtual_interface_id_refs_id_b058eaeb` FOREIGN
KEY (`backend_virtual_interface_id`) REFERENCES
`liquorstore_backendvirtualinterface` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=72184 DEFAULT CHARSET=latin1
I refer you to here:
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html
When I have had problems with MySQL not seeing names I knew to be there it usually had something to do with the settings above.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
