pbxt-discuss team mailing list archive

[Paul McCullagh <paul.mccullagh@xxxxxxxxxxxxx>]

Hi Tim, Brian,

Yes, this is a basic design decision in the engine. As far as I know  
the automatic order comes from the fact that InnoDB uses a "clustered  
index" to store the table data. This index uses the primary key order.

On Mar 23, 2010, at 7:27 PM, Tim Soderstrom wrote:

> Actually I thought that was a specific design decision with PBXT. I  
> recall Paul giving a talk where he mentioned the ordering being  
> different. I honestly do not remember why this was the case. Note  
> you can always order your dataset, optionally using the PRIMARY KEY  
> for that which is also likely to be fairly efficient (depending on  
> the query anyway). I was mostly pointing out the differences in  
> ordering of the rows on disk as being different between the two  
> engines.
>
> At least I think I explained that correctly :) Someone can throw me  
> under the bus if not though...
>
> Tim S.
>
>
> On Mar 23, 2010, at 1:23 PM, Brian Evans wrote:
>
> > 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
>
>
> _______________________________________________
> 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



--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com