Re: Managing different indexes for different databases
Pat, Now you've got me intrigued. Not to question the validity of this at all, but what does this do for the customer that leaving all the optional indexes on would? Do you, from the design mode, have all the optional indexes turned on, and turn off indexes based on the FieldMap settings? If so, if the Designer logged in would skipping the code that turns off these indexes allow a developer to work without it reindexing? Or, similarly, if a file called "Don't Reindex!" exists on the development machine, don't reset the indexes? Pat Bensky via 4D_Tech wrote: >In our app (CatBase) each customer can manage their own tables and fields >and one of the things they can do is specify whether a particular field is >indexed. Since these indexes are different for each customer, when they get >a program update from us, the indexes have to be recreated and built (there >is a FieldMap table which stores each field's attributes). This is n't a >problem for our customers, but for us developers, it means that if we are >working on several projects, each time we switch from one customer's >database to another, the indexes are all rebuilt. One project I'm currently >working on has about 4 million records and it takes ages to rebuild all the >indexes! The only way around it as far as I can see is to keep two copies >of the structure - one to use just with that database and one for all the >others. But that would introduce all kinds of possibilities for error ... > >Anybody got a better idea for managing this? > >Pat -- -- Tom Dillon 375 S Main St #405 DataCraft Moab, UT 84532 tomdil...@datacraft-inc.com 720/209-6502 -- Only the turtle strong enough to dig itself out of its sandy birthplace makes it to the sea to become a snack for the waiting barracuda. --- Sunastar -- ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: Managing different indexes for different databases
turn the indexes on the customer tables OFF? for development - indexed or not should not matter signifcantly. Chip On Fri, 14 Dec 2018 14:25:08 +, Pat Bensky via 4D_Tech wrote: > In our app (CatBase) each customer can manage their own tables and fields > and one of the things they can do is specify whether a particular field is > indexed. Since these indexes are different for each customer, when they get > a program update from us, the indexes have to be recreated and built (there > is a FieldMap table which stores each field's attributes). This is n't a > problem for our customers, but for us developers, it means that if we are > working on several projects, each time we switch from one customer's > database to another, the indexes are all rebuilt. One project I'm currently > working on has about 4 million records and it takes ages to rebuild all the > indexes! The only way around it as far as I can see is to keep two copies > of the structure - one to use just with that database and one for all the > others. But that would introduce all kinds of possibilities for error ... > > Anybody got a better idea for managing this? > > Pat > > -- > * > CatBase - Top Dog in Data Publishing > tel: +44 (0) 207 118 7889 > w: http://www.catbase.com > skype: pat.bensky > * > ** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** --- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Managing different indexes for different databases
In our app (CatBase) each customer can manage their own tables and fields and one of the things they can do is specify whether a particular field is indexed. Since these indexes are different for each customer, when they get a program update from us, the indexes have to be recreated and built (there is a FieldMap table which stores each field's attributes). This is n't a problem for our customers, but for us developers, it means that if we are working on several projects, each time we switch from one customer's database to another, the indexes are all rebuilt. One project I'm currently working on has about 4 million records and it takes ages to rebuild all the indexes! The only way around it as far as I can see is to keep two copies of the structure - one to use just with that database and one for all the others. But that would introduce all kinds of possibilities for error ... Anybody got a better idea for managing this? Pat -- * CatBase - Top Dog in Data Publishing tel: +44 (0) 207 118 7889 w: http://www.catbase.com skype: pat.bensky * ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
