명사
A user of the open-source relational database management system MySQL.
- 예문
-
Hello MySQLers, I set up some MySQL tables with timestamp fields.
For MySQLers, a helpful function is mysql_num_rows(), which is called on the query result ID and returns an integer.
더 많은 예문 (11)
Dear members, I know you are MySQLer^([sic]) but be honest, what is the the^([sic]) most used Database in ISP of webhosting, and the reasons. And fornyou,^([sic]) after MySQL what is the DB the^([sic]) you prefer in webhosting.
I'm a PostGreSQLer rather than a MySQLer, and looking through the mailing lists there it looks like theres^([sic]) been talk of accessing the XML as data rather than as text ...
MySQLers: No need to sort this stuff in PHP! Use MySQL's INET_ATON() family of functions to save cycles.
Why do we want this?? Because some apps have *lots* of data and many really don't care whether they lose a few records. Honestly, I've met people that want this, even after 2 hours of discussion and understanding. Plus probably lots of MySQLers also.
Andrii Nikitin, a MySQL support engineer located in Ukraine, has asked for help from MySQLers and I've decided to open this up to the community at large. Andrii's son Ivan, who is 2 1/2, is in need of a bone marrow transplant operation. This will require going to a clinic in Europe that will not be covered by regular insurance. […] Many MySQLers have kicked in to help out, but more is needed.
This is perhaps an implementation quirk of Postgres's, but it does have some advantages and we're not interested in giving them up just because it confuses MySQLers ;-). The main advantage is that having separate catalogs in each database is more robust (no matter how badly database A gets messed up, database B will be okay) and reduces contention for catalog access.
I'll point out that the MySQLers are enamored of the 3-byte integer, which even on MySQL saves zero space or memory over using a 4-byte. Just because people like it doesn't mean it works.
This one is targeted at you MySQLers: Polaricon recently upgraded to v2.0 its Jet Profiler for MySQL—a real-time query-performance and diagnostics tool for DBAs and developers.
Become a MongoDB DBA - What to Monitor (if you’re really a MySQLer)
The journey! That is the key point. MySQLers think about data as data stored into a database. When we think about the movement of data, we refer to it in terms of data extraction or data loading. The fact is, in IoT, data has value and it must be treated and considered when stored somewhere (data at rest) and when moving from one place to another (data in motion).
This is a world where DevOps Engineers need to be much better at performance than they currently are. Users do not support systems fail, so tasks for preparation and mitigation of failures become more important in a DevOps culture. Some activities for MySQLers include adding extra capacity, performance tuning queries and moving traffic away from unstable regions.
An employee of the Swedish software company MySQL AB.
용법- 역사 용어
- 예문
-
더 많은 예문 (3)
The big issues that I believe that people raised were: […] * Lack of clarity from MySQL on what is and not acceptable use of GPL-licensed MySQL […] Also, I have started discussing these issues with the other MySQLers and hope to have something useful to report soon.
MySQLers are also known to fire up a chat session on the side while on a conference call with a customer—the digital equivalent of kicking each other under the conference table.
I filed a support ticket with MySQL, which unfortunately isn't publicly available. […] This is some of my comments on the support ticket (#4053, in case MySQLers are watching!): […]
So, should it be considered as a bug or it is a feature? =3D) Please MySQLer's^([sic]) fix me if i am just wrong =3D)
더 많은 예문 (5)
> I thought this practice is deprecated, so I must send the hand-made propo= sed > patches to the Internals@ list exclusively... Well, probably I'm wrong. I > commit to my local clone, so you just get my notification e-mails. Yes, for patches contributed by non-MySQLers we still prefer reviewing and discussing them via the internals mailing list.
> This talk, was accepted. I would like to solicit professional (non > flaming) information on where people think MySQL can learn from > PostgreSQL. Well, frankly, I'm not much help. The reason why I never submitted a talk to MySQLCon, despite invitations, is that I couldn't think of content which would be both of interest to MySQLers and yet not improve MySQL's competitive position against PostgreSQL.
Several Sun MySQLers have been denied short stay business visas to Australia - yes, Australia - as they attempted to attend a Linux conference in Hobart, Tasmania. According to a blog post from Kaj Arno, vice president in charge of "database community" at Sun Microsystems, several employees - many of whom worked with MySQL - have been barred from entering Oz.
Forking is the sign of a robust developer community, argued Kaj Arnö, vice president of community relations in Sun's MySQL group. Arnö has been with MySQL since 2001, making this his second acquisition. "I have a phrase that I used to use last year: 'I cannot speak for Sun, because I am a MySQLer,'" he said during a post-keynote interview. "Now I have to do the same thing: I cannot speak for Oracle, but I will say that there are some things that an acquisition will not change. One is that MySQL has a huge user base. Another is that, though the founders and CEO are no longer with us, we have inside Sun some of the best MySQL experts. But most importantly, what has not changed is the license for MySQL. If you don't trust us, trust the GPL."
It's not clear to me that *Oracle* has ever had any particular view about DBD::mysql. It's not an Oracle product. It wasn't a Sun product before Oracle bought Sun. And as far as I am aware, it was not a MySQL AB product before Sun bought MySQL AB. It's true that MySQLers contributed some work to DBD::mysql, but as far as being any official company product ... I have never had that impression.