Shouldn't really matter for the example, it's standard ANSII SQL so should be ok on any server version.

__________________
Chris
Indifference will be the downfall of mankind, but who cares?
Code Samples | People Counting System

---

ASCII you mean? Well, it didn't work on my mySQL (is this how you say it..? lol..) and spit me an error that says I need to check the documentation. Since both servers are programmed differently interpreting codes, then that would matter

__________________

---

No I mean ANSII

<added on edit> Actually I mean ANSI (just the one I ) I'll blame the keyboard </added>

ASCII is something totally different.

__________________
Chris
Indifference will be the downfall of mankind, but who cares?
Code Samples | People Counting System

---

my bad then, that's just I'm the one that don't know what's ANSII What is ANSII anyway..?

__________________

---

ANSI *

Some acronyms you'll probably come to recognize at some point if you don't already:
ANSI = American National Standards Institute
ISO = International Standards Organization

As for ASCII, ASCII is an old 7-bit character set. Even when a byte was defined to be 8 bits instead of 7 bits later on, that 8th bit was unused because the idea was to maintain compatibility with older programs. IBM used that 8th bit by extending ASCII. It included various symbols and accented characters and other useful characters. However, this extended set of characters wasn't quite compatible internationally. In addition, other countries that had more characters than ASCII could handle, such as Chinese, used a completely different type of character set known as a DBCS (double-byte character set) or MBCS (multi-byte character set), which sometimes required only 1 bit to represent a single character, while others required 2 bits to represent a single character. There are various modern encodings that use the same idea as DBCS/MBCS such as UTF-8, UTF-16 and UTF-32.

__________________

---

but what does it mean by standard ANSII SQL

__________________

---

ANSII was a misspelling of ANSI. ANSI SQL simply refers to the SQL specification that was OK'd by the ANSI group. In other words, ANSI SQL refers to the ANSI standard of SQL. When something is a standard, usually it means that it is meant to be followed. Whatever is not defined is left open for other developers, like inline ASM. ANSI C doesn't define its syntax. In fact, ANSI C doesn't even define anything about ASM. It simply defines what the things in C should do and be and the syntax for using those things in C. I would expect the same to be true of ANSI SQL.

__________________

---

Well yeah, my professor also mentioned this. He said that most of the mySQL commands are compatible with others, but would others be compatible with mySQL he said that others may have an additional functionalities, while mySQL is strictly just following the standards queries

__________________

---

Hehe... Speaking of standards, I prefer to follow them as strictly as possible. HTML, XHTML, CSS, what bit of Java I know, C and C++... I do my best to keep the addons to the language down to a minimum. By addons, I mean things like an itoa function in C when no such function is defined by the ANSI C specification. Sure, most compilers support it, but do I use it? Nope. Not even for convenience. Not only that, but it is often easier to use my own function that does the same thing with less complication!

As for MySQL v.s. other SQL implementations, I'm not sure about much of anything about SQL, but I'd recommend going with your professor on this one.

__________________

---