comment on

Why are you comparing these two? If it's just curiosity, that's fine. If you're looking for a technology solution, have you identified your requirements?

Those are valid questions.

The database is going to be used as a librarian and a recorder of transactions. To me it sounds simple enough that MySQL would do fine, but the CTO wants to be sure that we can do things like views, triggers and rollbacks.

My preference is for MySQL because I know it very well and it has always performed admirably, but if the CTO wants to be able to the fancier things, that's cool. I just wanted to hear about any differences or gotchas that I should worry about.

And if it should happen that we don't use the fancy stuff, I can always go back to MySQL -- Perl lets me do that :) quite painlessly, I understand.

--t. alex
but my friends call me T.

In reply to Re: Re: Comparison, questions for Postgres, MySQL by talexb
in thread Comparison, questions for Postgres, MySQL by talexb

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks