RE: F/OSS Database experiences recommendations
On Thu, 2004-03-18 at 20:31, Dan Coutu wrote: I've created new users and granted them specific access to certain tables in a database via standard SQL. Seems pretty straightforward to me. No file was necessary. Isn't that what you were expecting? That certainly sounds better than what we had to do previously. In my copious free time (*wink wink*), I may have to pay PostgreSQL another visit. 8) -- Brooks's Law: Adding manpower to a late software project makes it later. Cole Tuininga Lead Developer Code Energy, Inc [EMAIL PROTECTED] PGP Key ID: 0x43E5755D ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: F/OSS Database experiences recommendations
On Wed, 2004-03-17 at 16:13, Dan Coutu wrote: Some of the really nice features of PostgreSQL are: *snip* We've been considering taking another look at postgresql. There was two things that were rather lacking last time we looked at it and I was wondering if you had any take on it: 1) Realtime replication was kludgy and unreliable. This is a requirement for us. Has anybody had recent experience with it? Is it any better? 2) User management just plain stunk. Defining users and their permissions were done in a very limited fashion in a setup file. Has this gotten any better? -- The best firewall is a pair of wire cutters. -Unknown, from the net Cole Tuininga Lead Developer Code Energy, Inc [EMAIL PROTECTED] PGP Key ID: 0x43E5755D ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: F/OSS Database experiences recommendations
Dan Coutu wrote: Interesting! I had not heard that they were planning to support triggers too. Thanks for pointing that out. Interesting to me too...I had not been following the goings on with MySQL too closely although I've been using it for a long time. Keep in mind that the MySQL v. 5.0 is considered the *development* version according to their own website (http://www.mysql.com/doc/en/MySQL_5.0_Nutshell.html). So stored procedures are not part of the 'stable' release which is still MySQL v. 4.0 -- FREePHILE We are 'Open' for Business Free and Open Source Software http://www.freephile.com (978) 270-2425 Work Hard. Rock Hard. Eat Hard. Sleep Hard. Grow Big. Wear Glasses If You Need 'Em. -- The Webb Wilder Credo ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: F/OSS Database experiences recommendations
On Thu, 2004-03-18 at 09:07, Cole Tuininga wrote: On Wed, 2004-03-17 at 16:13, Dan Coutu wrote: Some of the really nice features of PostgreSQL are: *snip* We've been considering taking another look at postgresql. There was two things that were rather lacking last time we looked at it and I was wondering if you had any take on it: 1) Realtime replication was kludgy and unreliable. This is a requirement for us. Has anybody had recent experience with it? Is it any better? I've not tried to do any replication with it. 2) User management just plain stunk. Defining users and their permissions were done in a very limited fashion in a setup file. Has this gotten any better? Well, maybe this is where not using older versions has me at a loss. I only know that it has create user and grant SQL commands that are typically used for managing users. On top of that I know they work! :-) I've created new users and granted them specific access to certain tables in a database via standard SQL. Seems pretty straightforward to me. No file was necessary. Isn't that what you were expecting? -- Dan Coutu Managing Director Snowy Owl Internet Consulting, LLC http://www.snowy-owl.com/ ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: F/OSS Database experiences recommendations
Thanks, Kevin. I am looking for something a bit more complex, and I probably should have explained that. I develop business applications involving dozens to hundreds of tables of data, and I'm looking to move some of these applications to a F/OSS backend from ISAM tables and/or Oracle/SQL Server back-end databases. I'm looking for database servers that run on Linux or cross-platform, and have tools to develop, test, maintain and tune them. Yes, it can all be done from the command line, but GUI or web-based tools to leave in the hands of my customer's DBAs have an advantage. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin D. Clark Sent: Tuesday, March 16, 2004 10:54 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: (no subject) Ted Roche writes: I would welcome experiences and opinions (like I have to ask!) on the various database backends available. If all you need to store are key/value pairs and you don't need SQL or network access, Berkeley DB is very nice/fast/reliable/portable. Regards, --kevin -- Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA) cetaceannetworks.com!kclark (GnuPG ID: B280F24E) alumni.unh.edu!kdc ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: F/OSS Database experiences recommendations
Ted Roche writes: I would welcome experiences and opinions (like I have to ask!) on the various database backends available. I've used both MySQL and PostgreSQL extensively. My take on them is that if you need something lightweight and fast to implement that non-DBA types can handle then use MySQL. If you need a full-fledged production database use PostgreSQL. Some of the really nice features of PostgreSQL are: - You can create your own functions use either the pgsql 'language' or are written in some other language such as C, C++, and so on. I'm using this capability to be able to have a function within the DB that generates GUID values. The function is actually written in C. (Note: The much ballyhooed MS SQL Server does *not* let you create functions of any sort. Bah!) - You can create stored procedures (MySQL claims this is coming). - You can define triggers (MySQL can't do this). - The time handling is exceptional. One place where I'm using the DB requires being able to display dates and times to users anywhere in the world using their own timezone. The time handling in the DB really helps a lot in making this job easier. (Note: not all timezones are a full hour apart from each other!) I know of no other database that can deal with time as well. Note that you can get GUI tools for administering it. The only one I've fooled with much runs on Windows though. It is the EMS PostgreSQL Manager. I believe there are a number of other tools out there that provide a GUI for you. -- Dan Coutu Managing Director Snowy Owl Internet Consulting, LLC http://www.snowy-owl.com/ ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: F/OSS Database experiences recommendations
- You can define triggers (MySQL can't do this). From: http://www.mysql.com/products/mysql/ Stored procedures and triggers Stored procedures allow you to create functions and subroutines that run on the server. This makes it possible to grant access to specific queries without granting carte blanche access to the underlying data, or validate data in the database before it is stored. Triggers can be configured to fire when certain conditions are fulfilled. The MySQL database server will provide hooks for implementing stored procedures in multiple languages, as well as including support for the Persistent Stored Modules syntax defined as part of ANSI SQL-99. Support for stored procedures was added in version 5.0, and support for triggers will be added in version 5.1. Plus they have some documentation for it already. http://www.mysql.com/documentation/maxdb/a7/41ee0b605911d3a98800a0c9449261/content.htm A friend of mine that uses MySQL says that it's in the dev version already. ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: F/OSS Database experiences recommendations
On Wed, 2004-03-17 at 16:46, Travis Roy wrote: - You can define triggers (MySQL can't do this). From: http://www.mysql.com/products/mysql/ Stored procedures and triggers Stored procedures allow you to create functions and subroutines that run on the server. This makes it possible to grant access to specific queries without granting carte blanche access to the underlying data, or validate data in the database before it is stored. Triggers can be configured to fire when certain conditions are fulfilled. The MySQL database server will provide hooks for implementing stored procedures in multiple languages, as well as including support for the Persistent Stored Modules syntax defined as part of ANSI SQL-99. Support for stored procedures was added in version 5.0, and support for triggers will be added in version 5.1. Plus they have some documentation for it already. http://www.mysql.com/documentation/maxdb/a7/41ee0b605911d3a98800a0c9449261/content.htm A friend of mine that uses MySQL says that it's in the dev version already. Interesting! I had not heard that they were planning to support triggers too. Thanks for pointing that out. -- Dan Coutu Managing Director Snowy Owl Internet Consulting, LLC http://www.snowy-owl.com/ ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
