To be honest the phrase was open to interpretation. In theory plain English should not be too hard, but in practice it is a language that can easily confuse: Time flies like an arrow, fruit flies like a banana.
Which could be (mis)interpreted to mean, "have you come here to look for people who are (already) on your team". Whereas, what you meant (I presume) was, "If you are here looking for people to join your team". It probably sounded correct to you in, and translated from, Dutch. But English has so many different ways to express things, it can catch you out. And that applies to native English speakers as much as to anyone else.
Since I do not speak any foreign languages (apart from American, and a few words of French, Spanish, Greek, Turkish and Hebrew) I have the greatest respect for people who can speak and write English, when it is not their native language.
When I see Greek or Hebrew I can only guess at the complexity.
Greek is quite easy because some of the letters are similar to ones we are used to. And some are math symbols which we often recognise. Hebrew is quite alien (and the wrong way round) but can still be learned with a bit of study.
hey guys, i'm developing a grocery store java desktop app, and i don't know much about databases and which one is better : an embedded data base or MySql,Postgres...considering performance and storage.
Both databases (MySQL and PostgreSQL) are very well known and have almost the same functionality. As to performance - it's opinion based only Joking! The thruth is that the performance depends on many factors, such as:
You are not running with a transaction log (see "The transaction log"). A transaction log improves commit time for transactions that insert, update, or delete rows.
You are using the 16-bit version of the Windows 3.x database engine. The 32-bit version has better performance, especially for larger databases.
You are loading huge amounts of data into a database. See "Tuning bulk operations" for methods to improve performance.
The database engine does not have an adequate amount of memory for caching database pages. See "The database engine" for command line options for controlling the cache size. Extra memory for your computer could improve database performance dramatically.
Your hard disk is excessively fragmented. This becomes more important as your database increases in size. The DOS and Windows database engines cannot do direct (fast) reading and writing when the database file is very fragmented. There are several utilities available for DOS and Windows to defragment your hard disk. One of these should be run periodically. You could put the database on a DOS disk partition by itself to eliminate fragmentation problems.
You are using a small page size for a large database. The page size is determined when the database is created by the initialization utility. You can find out the page size by using DBINFO. To change page size, you need to unload and reload your database.
The database table design is not good. A bad database design can result in time-consuming queries to get information from the database. If indexes will not solve your performance problem, consider alternative database designs.
Your hard disk is slow. A faster hard disk, a caching disk controller or a disk array can improve performance considerably.
In a multiuser environment, your network performance is slow.
You are fetching or inserting many rows of data. Consider using the multi-row operations.