[ATTN!] Inform us about your show-stoppers bugs in 2.4 betas if any!

[Dave Addey]

Hi Ruslan,

My tables are not dynamic - they never change their structure - but I do
need to delete all records very often.  I found that "drop" and then
"create" was a lot faster than "delete all records", and so I used the "drop
table" approach for speed.

If the speed is only a *little* faster when using the class-way, then I
think I will go for the API-way so I can drop tables safely :-)

I didn't know about the tmp files in v2.  I need to keep my data from one
launch to the next, so I probably won't use these - but they are useful to
know about.

Thanks for the help!

Dave.

> From: Ruslan Zasukhin <sunshine at public.kherson.ua>
> Reply-To: Valentina Developers <valentina at lists.macserve.net>
> Date: Sat, 08 Jul 2006 11:42:48 +0300
> To: "valentina at lists.macserve.net" <valentina at lists.macserve.net>
> Conversation: [ATTN!] Inform us about your show-stoppers bugs in 2.4 betas if
> any!
> Subject: Re: [ATTN!] Inform us about your show-stoppers bugs in 2.4 betas if
> any!
> 
> On 7/8/06 11:33 AM, "Dave Addey" <listmail1 at dsl.pipex.com> wrote:
> 
> Hi Dave,
> 
>> I understand now - thanks!  I changed my test project to use API-way, and
>> everything works fine.
>> 
>> I had been looking for an article like that one - it makes everything much
>> clearer.  It would be useful if you could add in some advantages and
>> disadvantages for the Class-way, to make it very very clear that the
>> structure is "fixed" when you use the class-way.
>> 
>> I shall change my code to use the API-way!
> 
> In fact you may be not need do this.
> 
> I have point that you can have N fixed tables, and few dynamic.
> Or all your tables are dynamic ?
> 
> Note also that in v2 exists ability create TMP table.
> This table will be stored not in .dat file but in hidden tmp volume.
> So after even crash of system your main .dat file is not affected.
> 
> 
> I think that 80% of RB developers use Class way.
> It is comfortable for app developers.
> And it produce even *little* faster code because you use direct pointers
> instead ask each time db.Table(Name)  and table.Field("name")
> 
> 
> -- 
> Best regards,
> 
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
> 
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
> 
> [I feel the need: the need for speed]
> 
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina