• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FrontBase license now free!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FrontBase license now free!


  • Subject: Re: FrontBase license now free!
  • From: Guido Neitzer <email@hidden>
  • Date: Mon, 8 May 2006 12:42:43 +0200

On 04.05.2006, at 18:23 Uhr, Pierce T. Wetter III wrote:

I seem to remember this getting fixed quite awhile ago. Are you still running into it? I know it was definitely fixed for the EOF case.

I have tested a statement 2 minutes ago and when I use something like

select * from foo where col1 like 'a' or col1 like 'b';

no index is used according to the query plan. With this I can use an in qualifier and then the index is used. But if I have

select * from foo where col1 = 'a' or col2 = 'a';

no index is used. I have a lot of queries like this because I have some "simple search" fields that search on several columns - and no, I can't use unions because I generally avoid using custom sql as long as I can because of maintenance issues we had in the past. It's not a problem right now because the tables are small enough so that result comes back in under 100ms but it may create problems for us in the future.

We will see.

- Has problems with some types of joins (extremely slow).

Sure, that's true of all databases, even Oracle/DB2/etc.

You're right. I can't test this right now because I don't have this problematic db running in FB anymore. For our other databases I would have to find problematic queries but as these are all much smaller (less then 20.000 rows per table) they are not obvious to see as the results come back mostly very fast.


Also this weren't complex queries - just joins over three tables (n:m relationship). Perhaps they made some progress on that, perhaps Geert can say.

FYI, if you turn on SQL logging, FrontBase has a tool that will replay your SQL operations in order, and they can use that to fix the bug pretty quickly.

I know. Pretty helpful. Also the transaction logs are sometimes helpful to see what happened when you have bad data in the db. I also love the backup strategy which simply works.


As a conclusion of having used Oracle (uah, long ago), FrontBase 4.x, MySQL 4.x and PostgreSQL 8.x I can only say that "it only depends on your needs". In the end you have to test your db schema with real data, real queries and with the amount of data you expect having in a couple of years on all dbms you evaluate for production and with a realistic load on the server.

The approach of using just one dbms for everything just don't work out very well because they all have goodies and problems.

cug

--
PharmaLine, Essen, GERMANY
Software and Database Development


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >FrontBase license now free! (From: "Pierce T. Wetter III" <email@hidden>)
 >Re: FrontBase license now free! (From: David Holt <email@hidden>)
 >Re: FrontBase license now free! (From: Chuck Hill <email@hidden>)
 >Re: FrontBase license now free! (From: David Avendasora <email@hidden>)
 >Re: FrontBase license now free! (From: "Pierce T. Wetter III" <email@hidden>)
 >Re: FrontBase license now free! (From: Guido Neitzer <email@hidden>)

  • Prev by Date: Re: FrontBase license now free!
  • Next by Date: problem while connecting to application via webserver
  • Previous by thread: Re: FrontBase license now free!
  • Next by thread: Re: FrontBase license now free!
  • Index(es):
    • Date
    • Thread