> Note that the license is usually negotiated with the > customer, so it may end up being one, two, or all of the > above, depending. MySQL AB, although they are (as I think > Lynn put it) "profiting on the confusion of the licensing > arrangements", they are also quite flexible in their > licensing and are willing to adjust things based on the > specific parameters of the application being distributed. (At > least, that's how they have been to me.)
That's true - but they cleverly put you into a situation where you have to come to them. Dang, why didn't I think of that first?;-) > As always, it's a "right tool for the right job" kind of > argument. There are many situations where > Valentina/PostgreSQL/mySQL/SQLLite/(fill in your favorite DB) > doesn't fit the bill. > > Just my 2 cents from personal experience, The market is packed full of dbs so developers have lots of choices. Valentina thrives because it has a unique underlying technology - so choose it if you fall in love with its unique features. The downside is that we don't wave the GPL flag. In a general sense though, I strongly urge anyone who has to make a choice to think about where your product/company is going to be down the road. If you ported to Revolution from another environment, you know that can be painful. Moving your customers to a new db back end also comes with its own special brand of pain. Best regards, Lynn Fredricks President Paradigma Software, Inc Joining Worlds of Information Deploy True Client-Server Database Solutions Royalty Free with Valentina Developer Network http://www.paradigmasoft.com _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
