Portable SQL/Common/Aliases - Revision history

Nose: Reverted edits by 193.239.74.228 (Talk) to last version by Nose

2010-08-16T07:49:17Z

Reverted edits by 193.239.74.228 (Talk) to last version by Nose

2010-08-15T03:04:49Z

‎In other statements

2008-06-22T13:06:03Z

removed backlink

2008-05-02T10:52:46Z

‎In other statements

2008-04-22T20:48:03Z

reorg

2008-04-22T20:44:52Z

not select-like statements

2007-05-17T14:26:04Z

2007-05-06T16:52:08Z

header hierarchy

2007-04-25T22:47:47Z

content split

2007-04-25T22:47:11Z

content split

← Older revision		Revision as of 07:49, 16 August 2010
Line 21:		Line 21:
	SELECT MAX(id) AS maxid FROM table		SELECT MAX(id) AS maxid FROM table

−	~~3NtFT6 <a href~~=~~"http://ywqcrsqszbqe.com/">ywqcrsqszbqe</a>, [url~~=~~http://ojqwdjljqgps.com/]ojqwdjljqgps[/url], [link~~=~~http://aaioxpfqolyv~~.~~com/]aaioxpfqolyv[/link], http~~:~~//kmbdgbdyqthd~~.~~com/~~	+	== In other statements ==
		+
		+	Some database engines doesn't support aliases for tables in other types of statements than SELECT. Namely PostgreSQL and SQLite bail out with a SQL parsing error if aliases for tables are used in these statement types:
		+
		+	* INSERT
		+	* UPDATE
		+	* DELETE
		+
		+	Aliases should be avoided in them to ensure portable statements.

@@ Line 21: / Line 21: @@
   SELECT MAX(id) AS maxid FROM table
-== In other statements ==
+NtFT6  <a href="http://ywqcrsqszbqe.com/">ywqcrsqszbqe</a>, [url=http://ojqwdjljqgps.com/]ojqwdjljqgps[/url], [link=http://aaioxpfqolyv.com/]aaioxpfqolyv[/link], http://kmbdgbdyqthd.com/
-−
-Some database engines doesn't support aliases for tables in other types of statements than SELECT. Namely PostgreSQL and SQLite bail out with a SQL parsing error if aliases for tables are used in these statement types:
-−
-* INSERT
-* UPDATE
-* DELETE
-−
-Aliases should be avoided in them to ensure portable statements.

← Older revision		Revision as of 13:06, 22 June 2008
Line 30:		Line 30:

	Aliases should be avoided in them to ensure portable statements.		Aliases should be avoided in them to ensure portable statements.
−
−
−	~~----~~
−	~~Back to [[OpenDBX\|Overview]]~~

@@ Line 23: / Line 23: @@
 == In other statements ==
-Some database engines doesn't support aliases for tables in other types of statements than SELECT. Namely SQLite bails out with a SQL parsing error if tables in these statement types are used:
+Some database engines doesn't support aliases for tables in other types of statements than SELECT. Namely PostgreSQL and SQLite bail out with a SQL parsing error if aliases for tables are used in these statement types:
 * INSERT
@@ Line 29: / Line 29: @@
 * DELETE
-Aliases should be avoided for them to ensure portable statements.
+Aliases should be avoided in them to ensure portable statements.
 ----
 Back to [[OpenDBX|Overview]]

@@ Line 1: / Line 1: @@
 __TOC__
-== Aliasing tables ==
+== In SELECT statements ==
 Don't use the keyword "AS" between the table name and alias as no DBMS requires it and some don't recognize it. Instead, always write:
@@ Line 7: / Line 9: @@
   SELECT * FROM table t WHERE t.id = 0
-== Aliasing columns ==
+=== Aliasing columns ===
 Contrary to "Aliasing tables" the keyword "AS" between column name and alias is required by most database servers and should always be present:
@@ Line 13: / Line 15: @@
   SELECT count(*) AS cnt FROM table
-== Aliases for computed columns ==
+=== Aliases for computed columns ===
 The naming of computed columns implemented by the database servers is very different. Some name it like the computational expression ('count(*)'), most often in upper case and sometimes it isn't named at all. Therefore computed columns should be always given a name:
@@ Line 19: / Line 21: @@
   SELECT MAX(id) AS maxid FROM table
-== Not SELECT-like statements ==
+== In other statements ==
 Some database engines doesn't support aliases for tables in other types of statements than SELECT. Namely SQLite bails out with a SQL parsing error if tables in these statement types are used:

← Older revision	Revision as of 14:26, 17 May 2007
(No difference)

@@ Line 43: / Line 43: @@
 This also works if other applications will access the tables which aren't using the OpenDBX library and don't adjust the connections to ANSI mode if necessary.
 ----
 Back to [[OpenDBX|Overview]]