Geoff Hutchison wrote: > > On Mon, 13 Dec 1999 [EMAIL PROTECTED] wrote: > > > old Berkeley DB files into SQL database. Trying to have a program able to > > handle both will lead to *very* hairy code. > > Yes, it probably would be very hairy. > > > No, the semantic is too different. In fact you could easily emulate > > Berkeley DB behaviour with SQL database. But that's not why you want a SQL > > database. You want to benefit from its versatility and ease of use. The > > nightmare will be to continue Berkeley DB compatibility while adding > > functionalities using SQL facilities. How do you emulate > > select * from table where value < 20 and string like "%foo" with Berkeley DB ? > > Surely you can, but at the expense of many lines of code. > > Personally I worry about this. I think that while many people want to see > a SQL backend, there shouldn't be a dependency on installing SQL. The > Berkeley DB is fairly lightweight, installed on many systems already, and > fairly robust. > > Yes, I agree that you don't want to emulate Berkely DB behavior with a SQL > database. However, we have much of the code for advanced features like > ANDs and ORs and LIKE in the code already. Moving to SQL would simplify > it, but should we just throw out this code? I think that this is the right way to approach this subject: Why do people want to use a SQL backend? Please correct me if I am wrong, but it seems to me that some folks just want SQL because they a) are familiar with it or b) already have a SQL database setup. What really needs to be described is the specific requirements that will force ht://Dig to move to an SQL database backend. Without that specification, the choice of moving to a SQL backend is silly and a waste of time and energy. > (My answer would be "no, we should see what features from SQL we would > *need* and think about how hard those would be for Berkeley DB with what > we have now.") > > -Geoff Hutchison > Williams Students Online > http://wso.williams.edu/ > > ------------------------------------ > To unsubscribe from the htdig3-dev mailing list, send a message to > [EMAIL PROTECTED] > You will receive a message to confirm this. -- Andrew Scherpbier <[EMAIL PROTECTED]> Contigo Software <http://www.contigo.com/>
begin:vcard n:Scherpbier;Andrew tel;cell:+1 858-361-4026 tel;fax:+1 858-278-2502 tel;work:+1 858-278-2329 x115 x-mozilla-html:TRUE url:http://www.contigo.com/ org:Contigo Software<br><img src="http://www.contigo.com/logo.gif">;Research & Development version:2.1 email;internet:[EMAIL PROTECTED] title:Chief Technology Officer note:<a href="http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=8334+Clairemont+Mesa+Blvd.&csz=San+Diego%2C+CA+92111&Get+Map=Get+Map">Yahoo Map</a> adr;quoted-printable:;;8334 Clairemont Mesa Blvd.=0D=0ASuite 204;San Diego;CA;92111;USA x-mozilla-cpt:;-5376 fn:Andrew Scherpbier end:vcard
------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
