16-Apr-2024 20:12 GMT.		 UNDER CONSTRUCTION
Anonymous, there are 12 items in your selection
[Files] MySql 4.0.0 for Amiga releasedANN.lu
Posted on 25-Oct-2001 15:28 GMT by Teemu I. Yliselä12 comments
View flat
View list
"This version is a major evolution of MySql, cause it will allow to add all missing functions of MySql such as as queries in the queries... This version have not been fully tested by MySql team that's why it is Alpha. The first new feature you will be able to test is Union queries, that work's fine." [This is the second, fixed release of the binary.]
Category: biz/dbase
License: open source		MySql 4.0.0 Alpha binary
Da SixK Port Page
MySql 4.0.0 for Amiga released : Comment 1 of 12ANN.lu
Posted by Anonymous on 25-Oct-2001 14:01 GMT
This is indeed great:) Problem is Amiga's current processor speed doesn't cope with the necessitites. But that will be solved very soon though;)
MySql 4.0.0 for Amiga released : Comment 2 of 12ANN.lu
Posted by John Adkins on 25-Oct-2001 14:28 GMT
I would suggest this be ported to PPC when/if a new OS becomes available. Apache+PHP+mySQL is one of the powerful combinations available in Linux, and is nice to see on Amiga. It allows you to make frontend interfaces (Apache+PHP), and pull your data from a database (mySQL). This is a much better alternative to something like Access datbases and VBScript. I think this would be a VERY important combo to port over to the new Amiga OS if/when it becomes available. The only other language that would be nice to have with Apache is PERL, and that is for all the applications already out there. I think overall PHP is the best pure web language out there (better then ASP, JSP, and Perl in my experiences).
The other VERY important thing I would like to see ported (but doubt we see something that big) would be OpenOffice (StarOffice). StarOffice 6.0 looks to be a GREAT alternative to Windows Office (except in the database area, which mySQL covers).
The last thing that needs to be ported is a good web browser. I think the current browsers out there can be imporved to be at par with some of the mainstream browsers, but something like Mozilla, or even better, talk them into a port of Opera for Amiga OS 4, would be nice.
I feel those 3 things above are VERY important things to be ported, and I would hope to see them in the new Amiga OS 4 in some way. I think they could jump start the Amiga BIGTIME. It would allow a full office package (Staroffice/OpenOffice, Apache/PHP/mySQL), and a nice browser to access the Internet (the big hub to the world). I think everything else can be filled in with current Amiga programs out there, or new programs specific to Amiga.
MySql 4.0.0 for Amiga released : Comment 3 of 12ANN.lu
Posted by Graham on 25-Oct-2001 15:23 GMT
In reply to Comment 2 (John Adkins):
PHP, JSP, Perl, ASP - they all have their place online, depending on what you are doing. For simple work, PHP is best, simple database access and scripting from within a HTML document - create a few nice templates for your site, and the correct code, and you are up and running. Easy as well.
Perl is good when you start doing more, or interfacing with other systems. It does everything, just one of its features is as a web language. Perl is one of MacOSX's official scripting languages. Once you know Perl, it is easy. With Perl, you write a script to generate the page. For a templated website, you can store the template in the same database as the data.
JSPs are great as well. Especially when used as an interface to a Java based system underneath, or just simply because of the simple to program, and fast platform it is, with nice OO notation, and the supporting libraries that provide features for everything. Lacks the nice regular expression stuff of Perl and PHP though, which is damned handy for parsing web forms.
ASPs are great if you are stuck with a crap Windows server and want to write your application to be restricted to a single platform. Yes, there are ASP-PHP convertors out there, but why not just write in PHP in the first place. However, ASP allows you to interface with Microsoft systems with ease (probably COM and all that malarky as well).
What I would like to see on the next generation AmigaOS 5.x based server is:
- Postgresql - a fast, open, RDBMS with full support for the SQL standard
- Apache
- PHP, Perl, Java, Python, and all those other languages that can be used (SHEEP!)
- REBOL
These should be packaged together into an Amiga Web Development Environment, with graphical IDE and all that stuff. Make all the components talk together nicely (they mostly already do). Putting a simple program together could be as simple as dragging and dropping "actions" together, and designing a UI. Hey, why not have the IDE create normal Amiga executable applications as well as dynamic websites? i.e., you can have either a web view of a site via a browser, or an application view (c.f., Outlook and Outlook webmail, but more consistent between the two).
MySql 4.0.0 for Amiga released : Comment 4 of 12ANN.lu
Posted by Martin Blom on 25-Oct-2001 15:27 GMT
In reply to Comment 2 (John Adkins):
Trust me when I say that PHP is definately not one of the best web languages ...
MySql 4.0.0 for Amiga released : Comment 5 of 12ANN.lu
Posted by John Adkins on 25-Oct-2001 16:05 GMT
In reply to Comment 4 (Martin Blom):
If PHP is not one of the best, then what is and why? Can't say it is not, and leave no reason why or alternatives?
MySql 4.0.0 for Amiga released : Comment 6 of 12ANN.lu
Posted by John Adkins on 25-Oct-2001 17:17 GMT
In reply to Comment 3 (Graham):
In response to what you said, I agree with about everything you said. I still think PHP is a BETTER web based langauge. Perl is considered the DUCK TAPE. It was made to work with WEB based stuff. I think Perl is the better one to use for server scripting (advanced shell scripting). But to use Perl for web development is like using PHP for server scripting. Can you use PHP for server scripting? Yes why not, just compile it into a standalone executable, rather then directly into a Apache module. You then call it like a Perl does. But why is PHP still better? 1) PHP is faster. I know that mod_perl helps close this gap, but mod_perl and perl run as a CGI have some programming style differences and this makes for a more of a pain. You can also compile PHP code (I know perl has some type of compiler floating around, but from peoples test's, it does not really speed things up much) with a add on to make it even faster, and also add the optimizer and cache to make it even faster. Perl CGI or mod_perl dont have this flexability, but commerical Servlet/JSP servers do. 2) PHP is a cleaner language. Perl syntax looks worst then anything I have ever seen. It is just hard to read. You find many site s on the internet talking about this. I agree that once you get the hang of it, it makes sense. It is a pain to get used to and pickup. PHP is much easier to pickup, and is more like C/C++. 3) More functions are built in to the lanuage. PHP has most Internet based stuff built into the language (FTP, MAIL, IMAP, etc). In Perl you must search the massive CPAN to find what you need, and then figure out how to use that module in a correct syntax matter. The PHP home page is much easier to use to find a function and how it works, then the Perl page. PHP has things more nicely organized.
Whats things do I like about perl? 1) It has been around longer so there is more programs and modules available for it. That means I have Perl around to run old programs, but not to develop new program in unless I am doing server side scripting. Its nice to use if it has a module that can be used to make a job easier, that is not available in PHP. 2) It is easier to port database applications because of the DBI interface. The DBI layer uses command function calls for all the databases, since the drivers run at a different layer. In PHP you have specific function calls for certain databases. This can be an advantage because you can have database specific features built in, but then makes porting it to another database a pain.
What about Servlets/JSP? Well you covered that by saying: "Lacks the nice regular expression stuff of Perl and PHP though, which is damned handy for parsing web forms.". Most of the Servlet,JSP engines cost $ (commerical) and can be expensive to scale. The free Servlet,JSP engines are still young and are open to bugs (the best I know is Tomcat from the Apache group). Servlets and JSP also don't help you much for things at the commandline like PHP and Perl can.
I think the best lanuage of course is the one you already know. If your new or want to learn a new language to develop web based applications, I would suggest PHP as the best from the above. If you will mostly do server based scripting, and a little amount of web apps, then Perl is your best bet. I would use Servlets and JSP only if you already know java or would like to learn some java.
I agree with you some what about ASP. ASP is good if you already know or want to learn VBScript (or Jscript, but VBScript has more flexability in a Windows enviroment). That is about it! You said use it if your stuck in a WIndows enviroment? WHY? Install PERL or PHP on your Windows machine. You also said something about COM support. You can do call COM objects from PHP.
You also mentioned Postgresql as compared to Mysql. I will not get deep into that in this message. All I will say is that YES Postgresql does support more of the SQL standard then mySQL, but is not 100% SQL standard (like Oracle, DB2). mySQL is missing major features (subqueries for one) that PostgreSQL has. These features will be added in the 4.0-4.2 release (mostly 4.0 and 4.1). 4.1 should be out in within 4 months. That means mySQL will have all those missing features. So where does Postgresql win then? Is it faster? NO mySQL is. Is the data handled better? NO mySQL is unless you like running VACUUM() all the time in Postgresql after doing a large amount of INSERTS, Is the table format and handling better? No in mySQL you can have multiple table types, so you pick the one that suits you. If you do only SELECTS, use the mySQL table format. If you do alot of INSERTS and need transactions and row/field locking, use InnoDB table format (InnoDB ROCKS, that is running Slashdot). Is the security better? No, how you set database rights sucks in PostgreSQL. You have much more control in MySQL. Also in 4.0 is SSL support. Is the OBDC driver beter? No, actually mySQL's driver is MUCH more mature then Postgresql. I could go ON and ON. mySQL will soon pass up Postgresql. So I would stick with mySQL if they are that close to having something, unless you need those missing things right now, then go with Postgresql. There is always a workaround to those missing features, but I dont like workarounds, since they invovle more work (using Perl or PHP of course).
You mentioned REBOL and SHEEP. Yes REBOL does look nice. Only bad thing about that is it is so different from other languages. Is that bad? Heck no! I think once you get used to REBOL, you will wonder why you put up with the other languages. Carl is doing a wonderful job with that. He has done ALOT in such a sort amount of time. He is basically going against .net. SHEEP also looks promising, and would expect that to be a native Amiga language.
Lastly you mentioned a package set. Well as it is now, Apache+PHP can be a package set. That is the web server and web scripting language. Need a programming IDE. Well another nice advantage to PHP is you can buy a very nice IDE for PHP. So use the PHP IDE and create your application. Use Apache+PHP to display it. Make a application that will create a shortcut to the web app display, and display it in a normal looking window. So basically it is a small web browser with everything stripped off. That way it looks like a normal application GUI. Use HTML to make your GUI look and forms (for this you will have to use something like Dreamweaver on Windows or MAC). What is nice about this solution as compared to what you said? Well it basically already available (except that stripped down web browser, but just use a regular web browser instead if something like thatis not around). I do like your suggestion, but that would involve someone working on a completely new IDE.
Well I think I wrote more then I expected, but hopfully I covered all the points.
MySql 4.0.0 for Amiga released : Comment 7 of 12ANN.lu
Posted by Anonymous on 25-Oct-2001 17:20 GMT
In reply to Comment 5 (John Adkins):
For the job it's intended for, I can't think of any alternative.
The only other solutions require me to reinvent the wheel or
force me to use a specific operating system.
MySql 4.0.0 for Amiga released : Comment 8 of 12ANN.lu
Posted by Don Cox on 25-Oct-2001 18:38 GMT
In reply to Comment 3 (Graham):
"What I would like to see on the next generation AmigaOS 5.x based
server is:
- Postgresql - a fast, open, RDBMS with full support for
the SQL standard
- Apache
- PHP, Perl, Java, Python, and all those
other languages that can be used (SHEEP!)
- REBOL "
AFAIK all of these are available now for AmigaOS, but you have to set
up a Geek Gadgets environment, and there are clashes between the
permission bits of files as set by AmigaOS and Unix.
I've used Apache with Perl on my Amiga for testing. MySQL is installed
but I haven't got around to trying it out yet - TBH it's easier to FTP
files to the real server.
The PostgreSQL port may be out of date.
MySql 4.0.0 for Amiga released : Comment 9 of 12ANN.lu
Posted by Graham on 25-Oct-2001 19:16 GMT
In reply to Comment 6 (John Adkins):
Thanks for the in depth reply - agree about the languages. PHP has a lot of momentum behind it for sure. I like Perl (took about a day to pick it up, and PHP was about a minute a year later), as it is very powerful - but yes, using it is like using C to write your dynamic web generator (yes, I have seen that done as well). I use Perl when I cannot use PHP, and because I use a database to store the templates in, and have a Perl CGI program that will allow me to edit them on-line without any shell access, which is nice. I can also edit PHP scripts this way I imagine - I haven't thought about it.
Tomcat is a very nice JSP engine that I recommend to people who know Java or a similar OO language.
MySQL loses most of its speed advantages over Postgresql when you use a table format that does row level locking. Future changes to MySQL will slow it down even more. Postgresql is gettng faster all the time - a year ago it was definitely slower, but now it is neck-and-neck. However, I agree that MySQL is easier to administer, and is good enough for most web based work. Postgresql is simply a higher end database than MySQL though, and I imagine it will stay that way for a reasonable time to come.
However, I am not stopping you running MySQL! My middle name is not "bill gates"...
MySql 4.0.0 for Amiga released : Comment 10 of 12ANN.lu
Posted by John Adkins on 25-Oct-2001 19:53 GMT
In reply to Comment 9 (Graham):
>Tomcat is a very nice JSP engine that I recommend to people who know Java or a >similar OO language.
I agree totally.
>MySQL loses most of its speed advantages over Postgresql when you use a table >format that does row level locking. Future changes to MySQL will slow it down >even more. Postgresql is gettng faster all the time - a year ago it was >definitely slower, but now it is neck-and-neck. However, I agree that MySQL is >easier to administer, and is good enough for most web based work. Postgresql >is simply a higher end database than MySQL though, and I imagine it will stay >that way for a reasonable time to come.
We will have to see when the 4.1,4.2 release is made (4.1 is supposed to be released by the end of December) and the lacking features are added. PostgresSQL still has a bunch of areas where mySQL is superior, so it better improve on more than speed. I still think mySQL is MUCH faster than PostgreSQL, and they are just trying to make it look fast so it equal to the area is always lost to mySQL in, speed. I would like to know if this benchmark is right: http://www.innodb.com/bench.html. It claims mySQL with InnoDB are MUCH MUCH faster then PostgreSQL and just ask fast as
MyISAM (mySQL's default format), and offers transactions and row/field locking.
I have read many good things about MySQL with InnoDB. Slashdot runs MySQL and InnoDB just fine, and you know how much of a load that site takes. The only thing bad I see about InnoDB is it is young, and is not as proven time wise as PostgreSQL. The good thing about both databases is that they are both trying to get to the same point, just starting from different directions. I just don't know how people will be able to put mySQL down so much after the next couple of version releases (when it fills in the major missing holes).
>However, I am not stopping you running MySQL! My middle name is not "bill >gates"...
Heheh. Yea I usually try to run what I consider the fastest, most stable, and easy/fun to use. I guess that is why I was (and want to be again) an Amiga user, you look for the best.
MySql 4.0.0 for Amiga released : Comment 11 of 12ANN.lu
Posted by SixK on 25-Oct-2001 21:26 GMT
In reply to Comment 10 (John Adkins):
Hi,
Just want to reply to a couple of mail here...
- apache+php is already available for Morphos. and I'm waiting for
a Morphos Pthread librairie (hope I'll not have to do it myself) to port MySql too.
- PHP or Perl ? I don't know what is the best, but I think you can do all that perl do with php
At my work we have rewriten all our Perl script to PHP.
- MySql against PostgreSql, dunno what is the fastest cause I never tryed PostGreSql,
but I think that MySql Optimiser is not really performant. when joining several Table, MySql
will make all possibles lines and then select then ones you need. The result is that what ever the order of you joins(column1=column2) or assign ( column1=1 and column2=2) the speed result will be the same.
If my memory is good, when I was using Oracle, if you put something like column1=1 and column1=column2, Oracle was first taking all the lines with column=1
and then join the line (column1=column2).
When MySql will have sub Queries it will then be able to force MySql to not join all the lines ;))
And maybe the MySql query optimisation will be improuved too. I'll talk about that with MySql team ...
Now, PostgreSql is not available for Amiga(or this is an old version) and will be really difficult to port
cause PostGreSql use modules that is not supported by Amiga Gcc (correct me if I'm wrong)
So there is no way to ask us what is the best...
SixK
MySql 4.0.0 for Amiga released : Comment 12 of 12ANN.lu
Posted by Graham on 25-Oct-2001 21:50 GMT
In reply to Comment 10 (John Adkins):
Slashdot is not actually that large a database, and it does have problems as the MySQL servers regularly crashes (ever go there when you are logged in, but you can't do anything except read the cached comment pages and you aren't logged in - that is when MySQL has crashed).
Postgresql is out there controlling 60GB databases now. http://www.us.postgresql.org/users-lounge/limitations.html
Scalability and reliability are worth a hit in the speed department. Remember, speed can be fixed with faster hardware. Reliability can't.
Still, I use MySQL as well as Postgresql. However, MySQL has lost orders for my company-on-the-side, so I might be biased against it.
Comparison review here:
http://www.webtechniques.com/archives/2001/09/jepson/
http://www.devx.com/dbzone/articles/renaker03/renaker03-1.asp
Anonymous, there are 12 items in your selection
Back to Top