| Thread Previous • Date Previous • Date Next • Thread Next |
Brian,PBXT uses ISAM-type table layout but I guess you can "emulate" InnoDB by creating a covering index consisting of your original candidate key + all fields from the table (except probably blobs and other heavy-weight fields). This way your tables will look to optimizer much like InnoDB tables with some exceptions like e.g. MySQL kernel knows that InnoDB automatically adds PK as suffix to all other keys, which will not be true for your PBXT tables. etc... Of course having a relatively large PK also influences performance as data will be written twice - to the table and to the index, but OTOH in PBXT indexes are not synched on commit so the penalty might be not that severe...
23.03.2010 20:23, Brian Evans пишет:
Is there anyway to make PBXT order ascending it's primary key automatically like InnoDB does? I know this is not how other engines like MyISAM work, therefore not a bug. But, we've switched our production machines to PBXT from InnoDB and some features may depend on this perceived default. _______________________________________________ Mailing list: https://launchpad.net/~pbxt-discuss Post to : pbxt-discuss@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~pbxt-discuss More help : https://help.launchpad.net/ListHelp
| Thread Previous • Date Previous • Date Next • Thread Next |
