Re: The best website database!
--- Basil Bourque [EMAIL PROTECTED] wrote: SNIP I did not catch the earlier part of this thread, but let me throw in my favorite db: FrontBase http://www.FrontBase.com/ It is native software, but runs on many Unixes, MS Windows, and Mac OS X, with a most excellent GUI admin tool for Mac OS X. It includes an excellent free JDBC driver (the best I've seen actually). FrontBase fully supports Unicode, and even uses Unicode internally for storing data. It is a commercial product, but has a free developer license, and a free deployment license (with some restrictions such as no backup feature). FrontBase is a mature, complete SQL database without the glaring holes in functionality that you'll find in hsqldb, Postgres, and MySQL. FrontBase stands out in its commitment to following standards, most especially the SQL92 standard. The makers of FrontBase go so far as to consider Date's book A Guide To The SQL Standard to be their documentation. http://www.bookpool.com/.x/isppqxs3im/sm/0201964260 Not saying you're wrong or right, but what do you see as the glaring holes in Postgres 7.2? And certainly not wanting to start any flame wars. SNIP = [EMAIL PROTECTED] Hacking is a Good Thing! See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The best website database!
--- Charles Baker [EMAIL PROTECTED] wrote: Not saying you're wrong or right, but what do you see as the glaring holes in Postgres 7.2? And certainly not wanting to start any flame wars. I started using Postgres about a year ago after many Oracle-based projects. The biggest things I have missed so far are that there are no built-in CONNECT BY, ROLLUP, and CUBE functions and the fact that Postgres seems to slow down significantly if it is not VACUUM'd frequently. However, these are not 'glaring holes' by any means and they should not deter you from using Postgres in any way, especially as an alternative to Access. By the way, there is a good solution for exporting data from Access to Postgres available open source from: http://www.rot13.org/~dpavlin/projects/sql/exportSQL3.txt (Just save as an Access Module and run -it creates the SQL statements to recreate the whole DB in Postgres) -August __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The best website database!
Hello Again Just to say thanks alot to all the people for their invaluable advice I am checking out all the different links. I will be most likely switching me database soon!!! Ok cheers Amran -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: The best website database!
Hi Amran, I am about to make a choice for our project. (jpass.sourceforge.net). Someone advice me to have a look at: http://hsqldb.sourceforge.net/ I haven't worked with it yet, so no valuable comments. but perhaps worth looking at. Cheers / Christophe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 30, 2002 10:13 PM To: [EMAIL PROTECTED] Subject: Re: The best website database! Hello Again Just to say thanks alot to all the people for their invaluable advice I am checking out all the different links. I will be most likely switching me database soon!!! Ok cheers Amran -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: The best website database!
hi, You could use oracle. For the UI part you could use TOAD, which is an excellent UI for doing all the operations required in Oracle. http://www.quests.com/ Regards, Vikramjit Singh, Systems Engineer, GTL Ltd. Ph. 7612929-1031 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 30, 2002 7:13 AM To: [EMAIL PROTECTED] Subject: Re: The best website database! Hello Again Just to say thanks alot to all the people for their invaluable advice I am checking out all the different links. I will be most likely switching me database soon!!! Ok cheers Amran -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The best website database!
Just to say thanks alot to all the people for their invaluable advice I am checking out all the different links. I will be most likely switching me database soon!!! I did not catch the earlier part of this thread, but let me throw in my favorite db: FrontBase http://www.FrontBase.com/ It is native software, but runs on many Unixes, MS Windows, and Mac OS X, with a most excellent GUI admin tool for Mac OS X. It includes an excellent free JDBC driver (the best I've seen actually). FrontBase fully supports Unicode, and even uses Unicode internally for storing data. It is a commercial product, but has a free developer license, and a free deployment license (with some restrictions such as no backup feature). FrontBase is a mature, complete SQL database without the glaring holes in functionality that you'll find in hsqldb, Postgres, and MySQL. FrontBase stands out in its commitment to following standards, most especially the SQL92 standard. The makers of FrontBase go so far as to consider Date's book A Guide To The SQL Standard to be their documentation. http://www.bookpool.com/.x/isppqxs3im/sm/0201964260 --Basil Bourque -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The best website database!
I've only witnessed one occasion where someone else was able to do something pretty cool with Access, but it was sufficient enough for Access to earn a bit of respect from me. I think many Tomcat users use MySQL and PostgresSQL due to the fact that they've got an open-source (as well as free) solution. At least I do; I can't afford Oracle, nor do I need it. Will, I use MySQL, and I'm happy with the MySQL Front free gui interface for it, however I don't think it's /quite/ what you're looking for. You don't design queries in MySQL (or in other apps I've seen) the same hands-off way you can in Access. Be this a blessing or a curse, I couldn't tell you. MySQL Front's website http://www.mysqlfront.de has some screenshots, check them out and see if they're helpful at all. Liam Morley Clay Graham wrote: well I have never heard any of my friends say MSACCESS is good for anything. most small tomcat sites that I know use MySql or postgresSQL, most big ones use Oracle 8i/9i clay -Original Message- From: Will Hartung [SMTP:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 6:10 PM To:Tomcat Users List Subject: Re: The best website database! - Original Message - From: [EMAIL PROTECTED] Hi All I currently use MS ACCESS as my backend to my website and other developers in the forum have advised this is not a good choice and I am aware of this but I was forced to use it as all data comes to me in MS ACCESS from database admin that supply the data for the website. I want to know what is the best database to use for a website? It Depends Now that that is out of the way... features I am looking for are: 1- An excellent GUI (Very important) front like MS ACCESS where I can quickly design queries, tables and so on. I normally design all the queries in MS ACCESS and then I just write the single line command SELECT QUERY1 rather than writing the full query in a javabean or jsp page by hand as this saves me alot of time. Ideally, you will, in time, wean yourself of this reliance, as most databases do not have a GUI. In the long term it's better to have a more intimate relathionship with SQL, minimally for performance reasons. But, it seems pretty clear you haven't reached that threshold yet. However, all is not completely lost. One of the Neat Things(tm) about MS ACCESS is not so much that it has a built-in database based on Microsofts Jet Engine, but that it can act as a central access point for, technically, any number of ODBC compliant databases. So, you can theoretically still use ACCESS as your primary database, but have all of the tables be linked from the true database host. This will certainly cost you performance, and the queries you devise may not work quite like they do in native ACCESS, but it will be close. Particularly if you are sticking close to the most basic of SQL functionality, and not relying on a lot of the higher level functions provided within ACCESS. If you're using mostly Pure SQL, then ACCESS is simply a data broker, and yet another layer between your app and your DB. As long as the contention and locking facilities are being used in the native backend, versus within ACCESS, you should gain quite a bit of reliablity over pure ACCESS as well. I'm not totally sure if this is the case, but it probably is, again for basic SQL statements. The goal is to use ACCESS simply as an interface into your new database, and have it broker your SQL statements to and from the database, with hopefully as little intervention as possible. Your SELECT QUERY1 will still work, however, but beware that ACCESS will potentially happily suck in all of the data from the new DB, churn on it, and then spit it back out to you. Depending on the query, this can be expensive and isn't what you want. If you like the simplicity of SELECT QUERY1 from ACCESS, I would suggest that you perhaps use ACCESS to develop your basic queries, and then use the actual SQL generated to turn them into VIEWS on the host DB, so the SQL in your Java becomes SELECT * FROM VIEW1. Again, it's almost always better to use the literal SQL rather than VIEWs, etc. ESPECIALLY if you're joining them together. SELECT * FROM VIEW1, VIEW2 WHERE ... CAN be very expensive. It all depends. But, when you data or activity gets big enough to actually notice the performance dogging, this kind of stuff tends to float to the top pretty quick, so when you need to fix it, you'll find it. These kinds of things work great with 10 rows in the tables, and die horribly with 1 rows. You WILL have issue with BLOBs of any kind, however. Of course, if you continue to receive data from your admin in ACCESS format, you will need a way to convert that data into the new back end. Ideally, this to can be automated from ACCESS as well: INSERT INTO NewBackEndTable SELECT * FROM OriginalACCESSTable. So, the point being, that even if you go to a new
RE: The best website database!
Hi Amram, Take a look at SAPDB (www.sapdb.org). It's free even for commercial applications, very scalable powerful, has plenty of functions, stored procedures, transactions, replication etc., a nice user interface in Windows. JDBC, ODBC, Perl and Python interfaces, a C/C++ precompiler and lots of documentation is available. For a simple website that doesn't require transactions this might actually be almost an overkill, and a lightweight db be more appropriate (like MySQL). SAPDB is closer to the big ones like Oracle. I personally like it a lot, unlike PostGreSQL it runs well on Windows. Markus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 6:05 PM To: [EMAIL PROTECTED] Subject: The best website database! Hi All I currently use MS ACCESS as my backend to my website and other developers in the forum have advised this is not a good choice and I am aware of this but I was forced to use it as all data comes to me in MS ACCESS from database admin that supply the data for the website. I want to know what is the best database to use for a website? features I am looking for are: 1- An excellent GUI (Very important) front like MS ACCESS where I can quickly design queries, tables and so on. I normally design all the queries in MS ACCESS and then I just write the single line command SELECT QUERY1 rather than writing the full query in a javabean or jsp page by hand as this saves me alot of time. 2- Good drivers (I know the MYSQL comes with Mark Mathews free drivers which are excellent - so i am preferabally looking for a cheap/free driver aswell). 3- Be able to export MS ACCESS databases (I would like to do this but not extremely important in long run as I might be able to convince my data suppliers to change databases) 4- Must be quite fast at processing alot of queries. I have done some reading on ORACLE, MYSQL (used it in university but was only text based!!! I know there are some GUI available but how good are they?), and SQL Server. Input welcomed from all Thanks in advance Kind Regards Amran -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 6/20/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 6/20/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The best website database!
I agree fully with Liam I'm an Apache/Tomcat user with a MySQL database, I use MySQL Front and have found it to be an excellent client application for accessing, importing and exporting data. Access can export data to CSV format which can simply be imported via MySQL Front for cross compatibility. Beware though, there are certain MySQL issue to be aware of: 1/ No support for UNION (at least in 3.23) 2/ No support for Sub-Queries 3/ No stored procedures or even stored queries/views (except in a sql text file). A variety of workarounds are available some of them more successful than others though. And it's not difficult to install. Best Regards, Anthony Geoghegan. J2EE Oracle Consultant. - Original Message - From: Liam Morley [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Saturday, June 29, 2002 10:14 AM Subject: Re: The best website database! I've only witnessed one occasion where someone else was able to do something pretty cool with Access, but it was sufficient enough for Access to earn a bit of respect from me. I think many Tomcat users use MySQL and PostgresSQL due to the fact that they've got an open-source (as well as free) solution. At least I do; I can't afford Oracle, nor do I need it. Will, I use MySQL, and I'm happy with the MySQL Front free gui interface for it, however I don't think it's /quite/ what you're looking for. You don't design queries in MySQL (or in other apps I've seen) the same hands-off way you can in Access. Be this a blessing or a curse, I couldn't tell you. MySQL Front's website http://www.mysqlfront.de has some screenshots, check them out and see if they're helpful at all. Liam Morley Clay Graham wrote: well I have never heard any of my friends say MSACCESS is good for anything. most small tomcat sites that I know use MySql or postgresSQL, most big ones use Oracle 8i/9i clay -Original Message- From: Will Hartung [SMTP:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 6:10 PM To: Tomcat Users List Subject: Re: The best website database! - Original Message - From: [EMAIL PROTECTED] Hi All I currently use MS ACCESS as my backend to my website and other developers in the forum have advised this is not a good choice and I am aware of this but I was forced to use it as all data comes to me in MS ACCESS from database admin that supply the data for the website. I want to know what is the best database to use for a website? It Depends Now that that is out of the way... features I am looking for are: 1- An excellent GUI (Very important) front like MS ACCESS where I can quickly design queries, tables and so on. I normally design all the queries in MS ACCESS and then I just write the single line command SELECT QUERY1 rather than writing the full query in a javabean or jsp page by hand as this saves me alot of time. Ideally, you will, in time, wean yourself of this reliance, as most databases do not have a GUI. In the long term it's better to have a more intimate relathionship with SQL, minimally for performance reasons. But, it seems pretty clear you haven't reached that threshold yet. However, all is not completely lost. One of the Neat Things(tm) about MS ACCESS is not so much that it has a built-in database based on Microsofts Jet Engine, but that it can act as a central access point for, technically, any number of ODBC compliant databases. So, you can theoretically still use ACCESS as your primary database, but have all of the tables be linked from the true database host. This will certainly cost you performance, and the queries you devise may not work quite like they do in native ACCESS, but it will be close. Particularly if you are sticking close to the most basic of SQL functionality, and not relying on a lot of the higher level functions provided within ACCESS. If you're using mostly Pure SQL, then ACCESS is simply a data broker, and yet another layer between your app and your DB. As long as the contention and locking facilities are being used in the native backend, versus within ACCESS, you should gain quite a bit of reliablity over pure ACCESS as well. I'm not totally sure if this is the case, but it probably is, again for basic SQL statements. The goal is to use ACCESS simply as an interface into your new database, and have it broker your SQL statements to and from the database, with hopefully as little intervention as possible. Your SELECT QUERY1 will still work, however, but beware that ACCESS will potentially happily suck in all of the data from the new DB, churn on it, and then spit it back out to you. Depending on the query, this can be expensive and isn't what you want. If you like the simplicity of SELECT QUERY1 from ACCESS, I would suggest that you perhaps use ACCESS to develop your basic queries, and then use the actual SQL generated to turn them
RE: The best website database!
Actually Desktop SQL is SQL Server, it's just a change in configurations (smaller default mem usage) and I believe a limited number of concurrent connections. It's also meant to work on Windows 95/98/ME. I also believe if it is run on 9x it doesn't support Named Pipes. As far as a good database for web development (specifically Java development), you can always look on the JDBC Driver support page. http://industry.java.sun.com/products/jdbc/drivers A Level 4 Driver is recommended because it theoretically allows for PURE Java development and portability. You may or may not want your product to be J2EE Compliant etc check it out. You will find just about everything, except Access I believe. You can also find out if it supports specific items such as connection pooling etc... As far as GUI interface development, there are plenty of tools out there; just they aren't included with the RDBMS most of the time. Try looking into Computer Associates ER Win or even (gasp) Visio Architect. And as far as your problem with your data coming in Access, you can always just write yourself a simple VB app that automates the moving your data from one format to another. The question I have is why are you moving the data. If the data was entered into a real RDBMS in the first place, you wouldn't be moving it, just accessing it differently. Maybe you need to find out why they are using Access and design a system that stops this manual Data massaging. Of course if you are looking for a reason to use Access, you have named them all. Easy development, Integrated GUI (sorta), low cost, and the data is already in Access. -Andrew -Original Message- From: Will Hartung [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 9:10 PM To: Tomcat Users List Subject: Re: The best website database! - Original Message - From: [EMAIL PROTECTED] Hi All I currently use MS ACCESS as my backend to my website and other developers in the forum have advised this is not a good choice and I am aware of this but I was forced to use it as all data comes to me in MS ACCESS from database admin that supply the data for the website. I want to know what is the best database to use for a website? It Depends Now that that is out of the way... features I am looking for are: 1- An excellent GUI (Very important) front like MS ACCESS where I can quickly design queries, tables and so on. I normally design all the queries in MS ACCESS and then I just write the single line command SELECT QUERY1 rather than writing the full query in a javabean or jsp page by hand as this saves me alot of time. Ideally, you will, in time, wean yourself of this reliance, as most databases do not have a GUI. In the long term it's better to have a more intimate relathionship with SQL, minimally for performance reasons. But, it seems pretty clear you haven't reached that threshold yet. However, all is not completely lost. One of the Neat Things(tm) about MS ACCESS is not so much that it has a built-in database based on Microsofts Jet Engine, but that it can act as a central access point for, technically, any number of ODBC compliant databases. So, you can theoretically still use ACCESS as your primary database, but have all of the tables be linked from the true database host. This will certainly cost you performance, and the queries you devise may not work quite like they do in native ACCESS, but it will be close. Particularly if you are sticking close to the most basic of SQL functionality, and not relying on a lot of the higher level functions provided within ACCESS. If you're using mostly Pure SQL, then ACCESS is simply a data broker, and yet another layer between your app and your DB. As long as the contention and locking facilities are being used in the native backend, versus within ACCESS, you should gain quite a bit of reliablity over pure ACCESS as well. I'm not totally sure if this is the case, but it probably is, again for basic SQL statements. The goal is to use ACCESS simply as an interface into your new database, and have it broker your SQL statements to and from the database, with hopefully as little intervention as possible. Your SELECT QUERY1 will still work, however, but beware that ACCESS will potentially happily suck in all of the data from the new DB, churn on it, and then spit it back out to you. Depending on the query, this can be expensive and isn't what you want. If you like the simplicity of SELECT QUERY1 from ACCESS, I would suggest that you perhaps use ACCESS to develop your basic queries, and then use the actual SQL generated to turn them into VIEWS on the host DB, so the SQL in your Java becomes SELECT * FROM VIEW1. Again, it's almost always better to use the literal SQL rather than VIEWs, etc. ESPECIALLY if you're joining them together. SELECT * FROM VIEW1, VIEW2 WHERE ... CAN be very expensive. It all depends. But, when you data or activity gets big enough to actually notice
