Re: MDB2_Schema question

Stoyan Stefanov wrote:

I was able to find a workaround by changing an MDB2 option: $mdb2->setOption('idxname_format', '%s'); The default option is '%s_idx'

thats the proper way to do things indeed.

Long story, short message. The question is: is this the expected behaviour? Or is it me or my MySQL install. I also have the suspicion that other areas of the XML result might be affected, like the constraints.

it is the expected behavior. mdb2 by default runs in maximum portability mode. for this to work mdb2 needs to enforce some specific datatypes and naming conventions. the aim is to have all of this optional. so the idea is that people can either "step into mdb2 portability world" and change their schemas accordingly and gain a very high level of portability. if they do not want to do this, they should just need to change a few options to be able to get around all of this portability stuff.

And last, when looking at the debug log ($schema->db->getDebugOutput()), I noticed queries like: SELECT MAX(sequence) FROM some_table_seq which should return the last consecutive number from the sequence table. This number is not in the XML result though. Is it normal? For the sequences I got only: <sequence> <name>some_table</name> </sequence>

You only requested to get a dump of the structure. But it seems odd that this query is still executed. Could you file a bug report on this, so I do not forget to investigate this? regards, Lukas