Index Corruption

[Silver Surfer-2]

We are seeing a lot of index corruption on V11 Mac   OSX 10.5.x.

It typically happens when we work on a structure on a local machine and then
move it to the live server.

It would be easier to understand if we were making structure changes to the
DB itself.  But we are only working with methods.

We are forced (out of safety) to rebuild the index file with each new
deployment.

But since we roll out incremental version twice a day and it takes 30
minutes to rebuild the index files,  this is less than optimal.

Im looking for any one who has and sort of a work around, or perhaps an
indication why we are getting the problem in the first place.
**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************

[Milan Adamov]

I had a similar problem with one application that is converted from v6  
to v11. It gave me constant number of errors on three indexes daily.  
The database used what is known as MacCroatian encoding and was  
converted to Unicode, I guess it has to do something with that because  
all three fields were Alpha type. Unfortunately, I had to turn the  
indexes off, because I couldn't find any other workaround.

Milan

On 06.11.2009., at 23.12, Silver Surfer wrote:

> We are seeing a lot of index corruption on V11 Mac   OSX 10.5.x.
>
> It typically happens when we work on a structure on a local machine  
> and then
> move it to the live server.
>
> It would be easier to understand if we were making structure changes  
> to the
> DB itself.  But we are only working with methods.
>
> We are forced (out of safety) to rebuild the index file with each new
> deployment.
>
> But since we roll out incremental version twice a day and it takes 30
> minutes to rebuild the index files,  this is less than optimal.
>
> Im looking for any one who has and sort of a work around, or perhaps  
> an
> indication why we are getting the problem in the first place.

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************