text:
Talk:Join (SQL)

New comments at the bottom of the page, please.

SemiJoins
what about semijoins

 * From the article:

 * A semi join is an efficient join method where first the join attributed of one table are collected and reported to the second one. In was first reported in 1981. It can be improved with a Bloom-Filter (hashing).

 * Yeah, it could do with a lot more detail. Neilc 13:59, 16 Apr 2005 (UTC)

 * The problem with the current description for semi joins is that it doesn't say anything at all: How is something reported? What means "collect" in the above sentence?  And how exactly would the improvement with hashing work?  I think that we either expand this to something comprehensible or remove it. --Stolze 21:50, 14 April 2007 (UTC)

I removed the semi-join stuff from the article because it didn't say anything meaningful. --Stolze 11:52, 8 May 2007 (UTC)

Images for join types
It would be good if someone would add images to help people visualize how each type of join is evaluated. I'm thinking that there should be drawings with the overlapping rings, highlighting the solution set. I would be willing to create them, however, I do not have experience loading images into Wikipedia. DBBell 21:08, 14 December 2005 (UTC)

 * I hope you don't mix this up with set operations like UNION, EXCEPT, and INTERSECT? If not, you could draw the images and we will incorporate them. --Stolze 12:19, 22 April 2007 (UTC)

A visual image might be to consider customers and orders. A left outer join would provide a set of all customers, whether or not the customer had any orders, PLUS the order records for those customers that had orders. It is possible that a customer might have no orders, so the business might want to delete him or her from the database, or send them a catalog.

A right outer join on the orders would be useful for that business to correct possible errors, since an order without a customer to pay for it would be a problem. This type of join would produce a set of records for all orders whether or not there was a customer related to it, PLUS the customer that ‘owns’ the order, so to speak.

In either type of outer join, it is only necessary to check for nulls in the related table to find ONLY those records that DO NOT have a related record in the related table.

Hope this helps ?Foresight2008 (talk) 03:52, 26 July 2008 (UTC)

here is an image: http://stackoverflow.com/a/4715847/4880924 --Kangaroo5Aust (talk) 00:35, 22 November 2015 (UTC)

Spanish language wikipedia has pretty images. Donalus (talk) 13:23, 13 September 2017 (UTC)

I added some of the Venn Diagrams from the Spanish language page. They also have an image that is similar to the one posted by Kangaroo5Aust, but it needs to be translated into English. Donalus (talk) 15:55, 13 September 2017 (UTC)

 * Surely these Venn diagrams are incorrect. The sets are disjoint and so there can be no intersection. For example when A is the set of employees and B is the set of Departments then the set of elements x where x is a member of A and x is also a member of B is {}. If A is the set of rows in table A and B is the set of rows from table B then the intersection of A with B is the {} since no row appears in both tables. Joins create tuples that is a concatenation of an A row with a B row. It would then be appropriate to consider the set of tuples. In the diagrams shown, A_tuple would be the set of A-B tuples where the rows from A which have a matching row in B as well as A rows which have no B match being substituted with null. B_tuple would be the set of complementary rows based on rows from B. The intersection of A_tuple and B_tuple would be joined rows with matching non-null values from both A and B. STACS-BM (talk) 22:10, 9 February 2024 (UTC)

I removed the image inner join, since it illustrated the concept with just an intersection. While the intersection of the sets being joined is important, it's not what an inner join is. Simply using an illustration of an intersection makes a false equivalence with sets, while values in a table do not have to be unique. Ivirshup (talk) 07:36, 22 December 2020 (UTC)

Left Outer Join
Just a quick question. Was it neccasary to have a "select _distinct_ *" in the code example for left outer joins?

 * It is not necessary. DISTINCT is a concept orthogonal to joins.  Therefore, I removed this keyword.

For those of us who work daily with SQl but have to look up the definition of 'orthogonal', "select distinct" should be assumed to be a crutch to fix a problem that may be solved more efficiently by other changes. Some experts with more experience than me recommend searching for any code that uses 'select distinct' as a quick means of identifying SQL that should be worked on to improve system efficiency. — Preceding unsigned comment added by 63.234.230.254 (talk) 16:04, 11 August 2014 (UTC)

Equi-Join Columns
I believe this might be an error. From the article:

 * The resulting joined table contains two columns named DepartmentID, one from table Employee and one from table Department.

If I'm not mistaken, this would be incorrect behavior under the SQL standard. I believe this is how it worked in earlier versions of MySQL, and possibly other DBMSs, but as per standard MySQL now only includes one instance of the join column.

Also, under Natural Joins, the order of the columns given may be incorrect (once again, possibly this is the actual order in some implementations). I believe the spec calls for the join columns to come first, and then the other columns of each table in turn.

I am basing this on the [MySQL docs], the part which begins:

 * The columns of a NATURAL join or a USING join may be different from previously. Specifically, redundant output columns no longer appear, and the order of columns for SELECT * expansion may be different from before...

Won't edit, as I don't think implementation docs are necessarily a good source for the standard, and I may be misunderstanding. DocAvid (talk) 21:03, 10 January 2008 (UTC)

 * You are correct, according to ISO/IEC 9075-2:2003 natural joins do suppress duplicate columns. This is from Section 7.7 (Syntax rules):

"7) If there is at least one corresponding join column, then let SLCC be a of s of the form COALESCE ( TA.C, TB.C ) AS C for every column C that is a corresponding join column, taken in order of their ordinal positions in RT1." It's stating that the resulting duplicate named column in the select list is the coalesced result from the columns of the same name in both table A and table B.SqlPac (talk) 05:51, 6 February 2008 (UTC)

It should be clearer what is meant by "A" and "B" in the article, i.e. which part of the sample query is the A table and which is the B table. (better yet, call the tables A and B to make it completely clear. —Preceding unsigned comment added by 70.66.236.249 (talk) 22:26, 19 March 2008 (UTC) Since SQL returns sets by default, the results would be DISTINCT because the duplicates cannot exist in a proper SET, as I understand it. Foresight2008 (talk) 03:42, 26 July 2008 (UTC) CL

The SQL standard deviates from the relational model in several ways even if it is supposed to be the standard language of relational databases, and all databases I know of deviate from the SQL standard. All DBMSs I know of will NOT allow you to create a table where multiple columns have the same name like "CREATE TABLE bad (col INT, col INT);" but most WILL let you run a query that results in multiple columns with the same name like "SELECT 1 AS col, 2 AS col;". More info at Relational_model. 139.80.112.182 (talk) 21:38, 11 December 2008 (UTC)

Equi Joins
From the article:

"SQL:2003 does not have a specific syntax to express equi-joins, but some database engines provide a shorthand syntax: for example, MySQL and PostgreSQL support  in addition to the   syntax."

This is not true. ISO/IEC 9075-2:2003 (E) defines the using syntax in 7.7, Joined tables:

This section should not have another example than the one used throughout the article. It is confusing to see a natural join demonstrated twice with two similar but different datasets. — Preceding unsigned comment added by 68.132.255.43 (talk) 15:39, 5 June 2017 (UTC)

Implicit outer joins
Does this article mean that SQL 2003 doesn't support implicit left/right joins using *= and =* syntax? 71.4.124.241 (talk) 18:10, 14 April 2008 (UTC)

 * ANSI/ISO SQL has never had that implicit outer join syntax. 155.4.126.237 (talk) 07:47, 24 May 2017 (UTC)

Full outer joins by left joins
I believe the example of how to construct a full outer join using only left joins is incorrect (the first one using outer left and outer right joins seems good). There is nothing ensuring that the two tables that are being unioned have the same column ordering. The correct fix would be to ensure that the second left join has the same column ordering as the first left join by instead of doing doing UNION SELECT * FROM  department doing UNION SELECT employee.*, department.* FROM  department You probably need a similar fix for the case of only using right outer joins. I verified that the command as shown does not work as stated in SQLite (version 3.4). Note that I am not a SQL expert though.

Foreign key error
The Sample tables section mentions the use of a foreign key:

"In the following tables,  is the primary key, while   is a foreign key."

This is incorrect given the definition of a foreign key [1], as it mentions: "The values in one row of the referencing columns must occur in a single row in the referenced table. Thus, a row in the referencing table cannot contain values that don't exist in the referenced table (except potentially NULL)."

Unfortunately, this seems to be the case, as the article itself says: "On the other hand, the employee 'Jasper' has no link to any currently valid Department in the Department Table." and as such this would violate the referential integrity constraint.

The examples are excellent, but I think it shouldn't be mentioned that it is a foreign key. I don't think it matters to the example anyway, because the presence of a foreign key is not required.

[1] http://en.wikipedia.org/wiki/Foreign_key —Preceding unsigned comment added by Svenmathijssen (talk • contribs) 10:04, 19 May 2008 (UTC)
 * Yeah. Department.departmentID is not a real Foreign Key, so the article should be changed.  Aar on Sc hulz  14:00, 19 May 2008 (UTC)

 * Foreign keys makes no difference when joining. You declare foreign keys to ensure data consistency (when INSERT/UPDATE/DELETE.) No need to confuse less experienced users here, talking about foreign keys. 155.4.126.237 (talk) 07:48, 24 May 2017 (UTC)

Computation of Cartesian product
From the article:

"The SQL-engine computes the Cartesian product of all records in the tables. That is, processing combines each record in table A with every record in table B. Only those records in the joined table that satisfy the join predicate remain."

I seriously doubt the SQL engine will explicitly compute the Cartesian product for such a query, especially in the presence of a clustered primary key on Department.DepartmentID further optimized by a sort order on Employee.DepartmentID (as the example suggests). The result can be thought of as a Cartesian product with the unnecessary tuples removed, but the engine will benefit from using the index. —Preceding unsigned comment added by Svenmathijssen (talk • contribs) 10:21, 19 May 2008 (UTC)
 * Yeah, it really would use the index and scan while joining with each row, otherwise it would be hella slow.  Aar on Sc hulz  13:56, 19 May 2008 (UTC)

Full outer join emulations
All emulations provided should be corrected to use UNION ALL instead of UNION as it is now. The reason:

1) queries work in these special cases because returned rows are unique both for left joins and right joins. However in case of duplicate rows these emulations would give incorrect result.

2) queries with UNION (rather than UNION ALL) need more database resources because database must filter out duplicates.

Example from the data as provided in article: Union gives us only unique rows: Union all gives us correct result: Gintsp (talk) 16:39, 28 July 2008 (UTC)

'''

About natural joins
User Mckaysalisbury under history page said: "natural joins are superior. Relational algebra doesn't even have a "join on", if you really think natural is prone to errors, that means you're using it wrong. Maybe we should axe the entire section?"

I completely disagree with this statement as well as I think it should be kept there. Writing SQL statements is not the same as dealing with Relational algebra - even more - many people writing SQL statements have never thought of Relational algebra. OK probably that's bad, but that's real life :) Also Natural joins ARE really evil with many possible side effects as I've explained it in my blog post and should be used with big caution. Also one of the SQL standard SQL-89 and SQL-92 authors Joe Celko said "Frankly, NATURAL JOIN was a bad idea. Any change to a table can suddenly add or remove a column in the join on the fly.  You do not know what you have done until you see both table declarations.  Much better to have explicit column names."

Gintsp (talk) 13:08, 15 September 2008 (UTC)

Please, if you are going to add a section on a type of join, please show the SQL code. This is, after all, a page on SQL joins, not the concept of "join" in general (if such a thing exists). Without any sample code, I have no clue how to implement this. Thank you. — Preceding unsigned comment added by 146.142.1.10 (talk) 21:59, 5 November 2015 (UTC)

MATHS?
I skimmed through and found no maths.

Why didn't anyone explain the joins from the correct relational point of view, which is formal/mathematical? —Preceding unsigned comment added by 193.136.19.11 (talk) 09:55, 2 October 2008 (UTC)

Response: for the theory behind SQL, see relational algebra articles. See Join_(relational_algebra) —Preceding unsigned comment added by 86.173.64.233 (talk) 14:54, 11 December 2008 (UTC)

Don't you think It would be a good idea to add this link to "see also" section in article? —Preceding unsigned comment added by 85.232.225.130 (talk) 17:54, 13 November 2009 (UTC)

Sentence doesn't make sense?
This sentence under "Natural Joins" doesn't make sense to me. I'm not sure what the intended meaning is, it seems like two sentences have run together (see emphasis):

An error-message such as "ORA-25155: column used in NATURAL join cannot have qualifier" is an error to help prevent or reduce the problems that could occur may encourage checking and precise specification of the columns named in the query, and can also help in providing compile time checking (instead of errors in query).

Xurizaemon (talk) 22:51, 12 March 2009 (UTC)

I Disagree with Reviewer's View that the Content Should Be Simplified
This article is very good. There is no end to the abundance of dummied-down, impractically simplified introductions to SQL on the net. And as far as I can tell this is exactly mid-level as far as SQL is concerned. The top of this page implies this is what it is aiming for. If you want advanced, follow the path of the abstract math that underlies the language. Nothing about this is advanced. If you work in SQL you run across other's SQL queries that are loaded with these kinds of joins. As an example, I am writing this addition because I was spinning my wheels on the FULL OUTER JOIN construct on no less than three SQL interpreters.

It is hard to find a reference that presents joins as comprehensively and concisely as this article. If you search the net for SQL tutorials, you will find few this clear and concise on this topic. I think it would be a real shame to dummy this article down (simplify).

--Ttreker (talk) 11:29, 25 April 2010 (UTC)

I also believe this is a very good article -- it's at the perfect level for me. — Preceding unsigned comment added by 174.6.76.165 (talk) 19:30, 25 September 2013 (UTC)

Additional Concern on Natural Joins from the Object Oriented Perspective
Natural join usage encourages naming conventions that run counter to the clean implementation of structured object oriented relational code wrappers.

If you are working in a relational system with an object-oriented wrapper to your relational objects, natural join naming conventions hinder solid polymorphic design. From an object perspective, you don't want primary key id fields named something different on each object. You want all of your objects responding to the same message (having the same method name), e.g. .id. This way if you have a heterogeneous collection of arbitrary objects, you know that you can send any of them the .id message and get it's primary integer key back. In other words, it doesn't matter what table the record is from, you always know .id will return the primary key. An example of just one of the many benefits of this approach is that if you combine this with a single sequence generator (generating unique key field values) for all of your id fields on all your relational tables, then it becomes easy to reference any arbitrary relational object by its id value alone, without reference to its table name even (building an application to achieve this is trivial). In other words, it is as if each object had its own UPC code. How ineffective would it be to reuse UPCs for each class of object in a grocery or department store? It should be clear to most people that this principle transfers naturally to software objects, at least where they map to real world objects.

From this perspective it is also redundant, for example, to have a department record with a field that calls it department_id or the like. With all deference to the survivors of the Monty Python troop, this is an example of "the department of redundancy department."

The OO approach:
 * department.id

The Monty Python approach:

 * department.department_id

The later naming convention is encouraged by the desire to employ natural joins.

In a data model supporting an OO wrapper, the convention of naming foreign key fields for the table that they reference is powerful. In this convention table names are *always* singular. This allows a foreign key field to simply be named for the table it references. The field name itself is singular or plural depending on the nature of the relationship between the tables, i.e. does it reference one, or many related objects.

With this paradigm, relational code wrapper generators can easily be written that read the database schema dynamically and generate object wrappers for relational records, tables, and result sets. If one has followed the conventions described above, the object code becomes immensely readable, and easy to write in an object oriented fashion. With such a consistent naming convention, the code wrappers written to implement joins (and other relational features) can be written on one superclass from which classes for each specific table can inherit. Adherence to such naming conventions allows, for example, for hiding the structure of intermediate tables used in many-to-many relationships. The underlying SQL necessary to support these structures can be be encapsulated in the superclass, which leverages the consistent naming conventions to achieve this.

I could gone on and on, actually. The power of this abstracted, polymorphic, and encapsulated approach is immense. It leads to a situation where the underlying relational structure melds seamlessly into the encapsulating code. This approach lends itself well to applications mapping software objects to the real world, and makes it easy for even novice developers to knock out some powerful applications without worrying about the mundane details of the structure of their queries. Many common queries can be auto generated dynamically in the superclass in this paradigm. More complex queries can be dealt with using naturalistic construction of "predicate" objects insulated from the nuances of SQL. This facilitates thinking problems through from the perspective of the business case being solved and not the underlying SQL. At the same time, all the power of this underlying SQL is fully leveraged.

Natural join field naming requirements are highly counter to this paradigm. They simply make a mess of it.

There are certainly situations where the above-outlined approach may be more of a hindrance than a help. There are no absolute rules in software development. But in applications that map real world objects to software objects, it is an extremely powerful approach. These kinds of systems are extremely common in our modern day world.

SQL developers may quickly zero in on the downside that there are a lot of duplicate field names across tables which makes ad hoc SQL queries using "select * from tab1, tab2" prone to confusion. However, in a properly structured system, these queries are not required as often as it may seem that they might be. And for ad hoc queries, many SQL user interfaces automatically disambiguate duplicate column names on the fly without user intervention. This is a common problem in SQL without consideration of the OO wrapper structure.

So how might someone make this point in this article in a succinct manner. Here is a shot:

 * "The use of Natural Joins in SQL encourages field naming conventions which present complications for object oriented wrappers. There is a fundamentally inherent asymmetry between primary fields and foreign key fields which suggests that they should not be named the same. As an example, from an object-oriented standpoint, all objects should respond polymorphically to an ".id" message by returning their primary key. Foreign key fields should be named for the table they address. This is counter to the implied requirement by Natural Joins that a primary key field and a foreign key field be named the same."

--Ttreker (talk) 03:48, 26 April 2010 (UTC)

I enjoyed your article, Treker, very informative. I disagree with your conclusion, however, as the wiki article is not about the OO paradigm or even about keys. Instead, i suggest something like this:

 * "Note the use of either JOIN--USING or NATURAL JOIN in SQL requires the field naming convention used above. An alternative naming convention, such as used in these table creations,

and which is perhaps just as popular, wouldn't work with JOIN--USING or NATURAL JOIN queries. It would require the ON form of query: " Martin F — Preceding unsigned comment added by 174.6.76.165 (talk) 20:10, 25 September 2013 (UTC)

Making content accessible to a wider audience is not tantamount to "dumbing down."
I can't tell whom that comment was for --possibly because what was being commented on was removed. But why see it as a zero-sum game? The art of writing is making the article accessible to a wider audience without making it less accessible to others. A few of the Wall Street Journal's Economics editors are masters of this: In a detailed article about the economy they will insert a concise elementary sentence --such as one would see in a primer-- clarifying what the "Fed" is, or what the inter-bank rate is, etc. This opens the article to a MUCH wider audience, yet it never registers with expert readers, who just fly over it without even noticing. It's not a distraction for experts.

Regarding: "Nothing about this is advanced. If you work in SQL..." Why write this article only for those who work with SQL? Such people have books on the subject, often acquired in school or other training. What do they need a Wiki article for?

Note that one of the reviewers (above) is a patent attorney. Who am I to say that a dairy farmer would not find this topic useful or enlightening? He somehow might even come up with a cure for cancer after reading this and some other articles? :^) Who knows?

CousinJohn (talk) 20:04, 26 May 2010 (UTC)

Are the insert examples really necessary?
I think the sql examples are mostly useful, but I wonder if the section demonstrating inserting data is really necessary. The article already gives visual tables of the data to be used in the examples. I'm not certain how showing how to insert this data really adds anything. The article is about joins after all, not data insertion. Removing them would make the article flow better I think. MaxMahem (talk) 03:18, 19 November 2010 (UTC)

 * Feel free to skip that section to preserve your flow. Cutting and pasting the code saves time and errors in constructing the sample tables.  —Preceding unsigned comment added by 69.171.176.210 (talk) 04:33, 4 January 2011 (UTC)

First mention of join
I have changed the type in the first mention of "join", as required by MOS:LEAD. (Also, as a reader, I found the Courier type confusing.) In my opinion, the article is mostly about the concept of a "join", not the syntax of a particular language. (I believe that joins are used in other languages than SQL.) It might be better to move the article to something like "Database join" and leave "Join (SQL)" as a redirect. If you do, remember the disamb page. --RoyGoldsmith (talk) 16:20, 24 January 2011 (UTC)

Motivation
It would be nice if there were an explanation for the typical motivation for using joins as opposed to a single table. I'm a newbie with respect to database design, so this was the (missing) information I was seeking when looking up the article.

 * → Database normalization. Jpatokal (talk) 02:34, 23 May 2011 (UTC)

Right outer join
The current text for right outer join states that they're rarely used because they can be replaced by left outer joins, but it doesn't provide any examples of why they might ever be used.

One situation I have occasionally found use for them is when I have a single table needing to be left outer joined to two inner joined tables. In this situation (assuming that the joins are all simple ID matches) you cannot simply left join table1 to table2 and then join table2 to table3, as any results for table1 which had no matches in table2 will be removed when the join from table1+table2 to table3 fails - the most common way of resolving this that I've seen is to left join table3 to table2, which works in the sense that table1+table2 results with null information for table2 will also receive null information for table3, but it leaves open the possibility of null results being attached for table3 to table1+table2 results which do have a table2 component.

In my mind it is a superior solution to first join table2 to table3, and then to right outer join the table2+table3 combination to table1. Another option is to join table2 to table3 in a subquery and then left join the results of that subquery to table1, but this makes the query more complicated than necessary. --210.11.199.87 (talk) 05:05, 24 March 2011 (UTC)

Self join example
I think the example given in the Self Join section -- finding pairings of employees in the same country -- is too unreal to be helpful, and request that it be replaced with the fairly standard parent-child example of listing all employees along with the name of their manager. Matthew C. Clarke 07:33, 20 May 2011 (UTC)

Joining more than two tables - Comments on Inner Joins
I wonder if this article should have a section about joining three or more tables. I seem to remember that there's a faster way to do this that doesn't come from a Cartesian product of the three tables, but from the (smaller) Cartesian products of two of the tables, the results of which are processed in another Cartesian product with the third table. This speeds things up. Does anybody know any more about this? —MiguelM (talk) 03:10, 7 July 2011 (UTC)

Most real-world queries involve more than two tables. Have never even imagined a Cartesian product of three tables produced in a single operation. Don't think that a three-way inner join exists except in theory. The execution cost could be enormous compared to other methods. Three tables inner joined would probably be processed in order, with the inner joined results from the first pair inner joined to the last table. The execution plans produced by database managers would bear this out (my experience is with MSSQL). The actual order of the inner joins may be subject to change by the database's optimizer based on statistics. If one of the inner joins is more selective (reduces the record set to a relatively small number) than the other, the optimizer may reverse the order to reduce cost. This would not be obvious unless you review the actual execution plan but the results should be the same.

I work every day creating complex SQL queries in a reporting database and don't even bother to count the number of tables joined together in a query. A dozen would be typical, 20-30 in a single view or stored procedure is not surprising. Tables range from a handful of rows to 3-billion, four fields per table to 120 or more, multi-gigabyte sizes for many tables.

When querying a reporting database I've never been concerned about cartesian products (except when making a mistake in the join fields). Using MSSQL and no doubt other databases, the optimizer takes care of the details.

This article is very misleading in that it encourages inner joins at the exclusion of others. Who says they are the most common or default? The wording says "for applications". I have never read that anywhere else and have spent many hours studying books written by leading experts.

My method for years is to typically use left outer joins (MSSQL) and inner joins rarely, only where it has been proven by tests that NULL values won't eliminate data/returned rows along with deleting related information from other tables. My database doesn't encforce referential integrity, and that design decision is not something I control. Right outer and Full outer joins are pretty rare but have come up. Use UNION of queries many many times.

Inner Joins are NOT always faster than Left outer joins. Any complex query has many other considerations than just slamming in inner joins everywhere. Have seen inner joins kill a server as it matched up two tables with tens of millions of records before filtering the data and returning a list of fields. Speed of processing isn't the only consideration.

IF YOU USE AN INNER JOIN AND DON'T REALIZE THAT A TABLE HAS SOME NULL VALUES ON THE JOIN KEYS THE DATABASE WILL SILENTLY DISCARD BOTH SIDES OF THE JOIN! NO ERROR MESSAGE. YOU WILL GET ENOUGH DATA TO THINK IT'S CORRECT BUT WILL BE WRONG IN A SMALL WAY EVERY TIME!! OR IF THERE ARE A LOT OF NULLS YOU WILL BE WRONG IN A BIG WAY!!!

When joining a large number of tables you need to know your data. Table record sizes, expected number of rows selected, whether indexes are available that cover all of the fields that you want returned so the database doesn't have to plow through the entire table. Then it can be structured using a variety of methods to 'get the number of records down to the smallest number as soon as possible". After that, everything is efficient or if it isn't it doesn't matter.

Nested queries, correlated subqueries, derived tables, common table expressions, functions, temp tables, custom indexed tables, multiple sequenced queries in a stored procedure are ways to structure complex queries. They all belong in your bag of tricks, along with the knowledge of where they are best used. Learn as you go, figure out how to use the tools to get cost figures and record time and cost results as you make changes. The query will get faster (or you will backtrack so always make multiple backups).

Everyone seems to want the faster code, maybe to support transaction processing which typically involves a small number of tables, limited number of fields, updating minimal number of rows in a controlled process. This isn't NASCAR. Speed is important but accuracy is more important (still efficiency IS important).

Natural Join section is unclear
I added a clarifying sentence to the section on Natural Joins, explaining why they're dangerous. Without it, it's not at all clear what the difference is between natural joins and equijoins, and it made me want to avoid both of them. —MiguelM (talk) 03:46, 7 July 2011 (UTC)

implicit "OUTER" for LEFT JOIN?
I am confused. :-( --RokerHRO (talk) 12:10, 13 July 2011 (UTC)
 * Is LEFT OUTER JOIN the same as LEFT JOIN in standard SQL?
 * Fulfill MySQL, PostgreSQL etc. this standard?
 * Why do exist different symbols for "LEFT JOIN" (⋉) and "LEFT OUTER JOIN" (⟕)?

The OUTER keyword is optional. I.e. LEFT JOIN means LEFT OUTER JOIN, and RIGHT JOIN means RIGHT OUTER JOIN. (In both cases there are an "outer" table.) — Preceding unsigned comment added by 192.71.97.254 (talk) 09:17, 19 October 2011 (UTC)

I found this article to be confusing
Why are there two natural join sections? Why does it not use the example introduced at the top consistently? — Preceding unsigned comment added by 84.154.15.166 (talk) 19:14, 7 December 2014 (UTC)

Please add a section about "LATERAL JOIN"
See https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.3#LATERAL_JOIN — Preceding unsigned comment added by 89.246.199.104 (talk) 11:31, 30 May 2015 (UTC)

Natural join is described in two places now
Both by itself, and inside Inner Join. The two should be merged. ★NealMcB★ (talk) 00:46, 23 December 2015 (UTC)

 * NATURAL JOIN is just a special case, of either INNER JOIN or OUTER JOIN. Keep things together, i.e. no main section for NATURAL JOIN. Also JOIN USING syntax should be placed under INNER and OUTER JOIN. 155.4.126.237 (talk) 07:48, 24 May 2017 (UTC)

Natural join does not have an SQL example
It would be great to give an SQL example for a natural join, because I was trying to distinguish between a natural join and an inner join, it seems like inner join is a superset of natural join, is it perhaps less efficient? All the other types of joins have exmaples; please add an SQL example for natural join. SystemBuilder (talk) 18:06, 5 May 2016 (UTC)

 * A NATURAL JOIN can be either an INNER JOIN (select ... from t1 NATURAL JOIN t2), or an OUTER JOIN (select ... from t1 NATURAL LEFT JOIN t2). 155.4.126.237 (talk) 07:49, 24 May 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Join (SQL). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20121216123745/http://www.coffingdw.com/sql/tdsqlutp/join_index.htm to http://www.coffingdw.com/sql/tdsqlutp/join_index.htm

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 12:40, 26 April 2017 (UTC)

Example queries in section "Inner join" are not equivalent
In section Inner join, the statement, "The following example is equivalent to the previous one, but this time using implicit join notation:" is false because the two example queries are not equivalent and do not produce the same result. In order to make the two queries equivalent, the second query should read:

and the query result should read:

--RedViking20200702 (talk) 06:57, 11 August 2020 (UTC)

I corrected the second query as I described in my previous comment.

--RedViking20200702 (talk) 07:03, 11 August 2020 (UTC)

Join index section
The section on join indices probably needs (in 2022) attention by someone knowledgeable in the matter. Specific issues: 90.129.219.218 (talk) 10:32, 21 March 2022 (UTC)
 * 1) It places great emphasis on summarising the capabilities of specific products, and given that it cites the year 2012, there is a definite risk that this information is now outdated.
 * 2) It fails to explain how a join index is any different from an ordinary index. The way it describes these indices — that they are updated when the underlying tables change, that they cover a subset of the columns, etc. — sounds very much like the way an ordinary index works. I suspect that the key point is that a join index combines data from several tables, whereas ordinary indices would not, but the article should state the matter explicitly.

"Join (SQL" listed at Redirects for discussion
An editor has identified a potential problem with the redirect Join (SQL and has thus listed it for discussion. This discussion will occur at Redirects for discussion/Log/2022 October 27 until a consensus is reached, and readers of this page are welcome to contribute to the discussion. Steel1943 (talk) 19:41, 27 October 2022 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Talk:Join (SQL)


text:
Talk:Internet2

== Internet2 doesn't "develop technology" ==

It is one of many enablers of the development of technology.

I removed the statment about Internet2 developing technology such as IPv6, multicast, and QoS. These technologies and research has involved hundreds of researchers and perhaps thousands of engineers, much of which predates the existance of Internet2 and most of which had nothing whatsoever to do with Internet2. -- James Sterbenz, EECS/ITTC, The University of Kansas

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on Internet2. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20100206022549/http://www.internet2.edu/wg/wg-list.html to http://www.internet2.edu/wg/wg-list.html
 * Added archive https://web.archive.org/web/20090813013302/http://www.internet2.edu/meetings/ to http://www.internet2.edu/meetings/
 * Added archive https://web.archive.org/web/20061020085946/http://www.internet2.edu/termsofuse.html to http://www.internet2.edu/termsofuse.html
 * Added archive https://web.archive.org/web/20080605211341/http://www.internet2.edu/idea/ to http://www.internet2.edu/idea/
 * Added tag to http://beryl.cse.ucsc.edu/video/Distinguished_Lectures/Houweling2_4.wmv

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 12:49, 15 November 2017 (UTC)

Semi-protected edit request on 16 May 2019
ADD TO THE HISTORY SECTION:

In 2010, Internet2 received a 62.5M American Recovery and Reinvestment ACT grant [reference https://www2.ntia.doc.gov/grantee/university-corporation-for-advanced-internet-development] that allowed Internet2 to put in place a long term IRU for fiber and upgrade the network with its own DWDM optical network system. Ciena later announced that this was the first 100G nationwide optical network. reference: https://www.ciena.com/insights/case-studies/Internet2-Building-Americas-First-National-100G-Network.html The upgrade to the new optical system was complete in December, 2012. Reference: https://www.internet2.edu/blogs/detail/4630 Rvietzke (talk) 12:17, 16 May 2019 (UTC)
 * Yes check.svg Done NiciVampireHeart 11:31, 22 May 2019 (UTC)

title: Talk:Internet2


text:
Ministry of Transportation of Ontario

The Ministry of Transportation (MTO) is the provincial ministry of the Government of Ontario that is responsible for transport infrastructure and related law in Ontario, Canada. The ministry traces its roots back over a century to the 1890s, when the province began training Provincial Road Building Instructors. In 1916, the Department of Public Highways of Ontario (DPHO) was formed and tasked with establishing a network of provincial highways. The first was designated in 1918, and by the summer of 1925, sixteen highways were numbered. In the mid-1920s, a new Department of Northern Development (DND) was created to manage infrastructure improvements in northern Ontario; it merged with the Department of Highways of Ontario (DHO) on April 1, 1937. In 1971, the Department of Highways took on responsibility for Communications and in 1972 was reorganized as the Ministry of Transportation and Communications (MTC), which then became the Ministry of Transportation in 1987.

Overview
The MTO is in charge of various aspects of transportation in Ontario, including the establishment and maintenance of the provincial highway system, the registration of vehicles and licensing of drivers, and the policing of provincial roads, enforced by the Ontario Provincial Police and the ministry's in-house enforcement program (Commercial vehicle enforcement).

The MTO is responsible for:
 * 10.4 million vehicle registrations
 * 8.5 million driving licences
 * 55 driver examination centres and 37 travel points (both operated by Plenary Serco (PS) DES, as DriveTest Centres)
 * 281 privately owned Driver and Vehicle Licence Issuing Offices across the province
 * Metrolinx (responsible for GO Transit, Union Pearson Express, and Presto card)
 * 16 525 kilometres of provincial highways
 * ServiceOntario kiosks
 * Commercial vehicle enforcement program vehicles and infrastructure (varies annually).

History
Early roads in Ontario were cleared when needed for local use and connections to other settlements. Key roads such as Yonge Street and Kingston Road were cleared by order from officials by various parties such as settlers, British Army units (portion of Yonge c. 1795 Queen's Rangers) or private contractors (Toronto to Trent section of Kingston Road c. 1799-1800 by Asa Danforth). Road standards varied (poor in winter or after rainfall) and used by horses or horse drawn stagecoaches.

With the arrival of motor vehicles proper road development an maintenance was needed. The earliest Ontario government office responsible for roads and transportation was the position of the Provincial Instructor in Road-Making, first appointed in 1896 and attached to the Ontario Department of Agriculture. A.W. Campbell held the position of Provincial Instructor in Road-Making from 1896 to 1900 and Director of the Office of the Commissioner of Highways from 1900 until 1910. He was tasked with training Provincial Road Building Instructors. These instructors worked to establish specifications for the almost 90,000 km of county- and township- maintained roads.

The name of the office was changed to the Commissioner of Highways and transferred to the Department of Public Works in 1900. By 1910, the office was generally referred to as the Highways Branch. In 1910, W.A. McLean, Provincial Engineer of Highways, succeeded A.W. Campbell as the director of the Highways Branch.

Under considerable pressure from the Ontario Good Roads Association and the ever-increasing number of drivers, which the province itself licensed at that time, the Department of Public Highways was formed in 1916 with the goal of creating a provincial highway network. The department assumed all the functions of the Highways Branch. The department assumed its first highway, the Provincial Highway, on August 21, 1917. On February 20, 1920, the department assumed several hundred kilometres of new highways, formally establishing the provincial highway system. Although established as a separate department, the Department of Public Highways shared ministers with the Department of Public Works prior to 1931 and seems to have been in a quasi-subordinate relationship with this department.

In 1916, the Motor Vehicles Branch was established within the Ontario Department of Public Highways. Prior to this, responsibility for the registering and licensing of motor vehicles rested with the Provincial Secretary (a responsibility it held since 1903). Although there are references to motor vehicle licensing and registration between 1916 and 1918, there is no mention in the Annual Reports of what agency actually performed this function; it is, however, likely that it was a form of, or precursor to, the Motor Vehicles Branch. In 1919, a Registrar of Motor Vehicles, as head of the Motor Vehicles Branch, is clearly identified.

In 1917, the Provincial Highway Act was passed, giving the department authority to maintain and construct leading roads throughout the province as provincial highways (designated King's highways in 1930). The Department of Public Highways was renamed the Department of Highways in 1931 and was assigned its own minister, Leopold Macaulay, though Macaulay later held both portfolios in 1934.

In 1937, the Department of Northern Development, previously responsible for highways in the northern parts of the province, was merged into the Department of Highways, thus bringing all highway work in the province under one administration.

On July 1, 1957, legislation was passed which established a separate Department of Transport, and the Motor Vehicles Branch was transferred to this new department. The new department assumed responsibilities for vehicle licensing, vehicle inspection, driver examination, driver licensing and improvement, traffic engineering, accident claims, and highway safety. In addition, it was responsible for the Ontario Highway Transport Board.

In May 1971, the Department of Transport and the Department of Highways were amalgamated to form the Department of Transportation and Communications. The new department was presided over by the Charles MacNaughton, who had been both the Minister of Highways and the Minister of Transport prior to the amalgamation. The department was renamed the Ministry of Transportation and Communications in 1972 as part of a government wide reorganization.

In September 1987, the responsibilities for communications were transferred to the Ministry of Culture and Communications, and the ministry was renamed the Ministry of Transportation.

Road maintenance
Maintenance work is performed in two different ways:
 * 1) In Maintenance Outsource areas, where MTO staff monitor the road conditions and hire contractors on an as-need basis.
 * 2) In Area Maintenance Contract areas, where one contractor is awarded a contract area and performs all maintenance work except for rehabilitation and new construction.

A list of Area Maintenance contractors currently under contract with the MTO includes:
 * Emcon Services Inc.
 * Ferrovial Services
 * Fowler Construction Company Ltd.
 * IMOS (Maintenance performed by Miller Maintenance)
 * C-Highway Maintenance Contracting Inc.
 * The 407 ETR Concession Company operates and maintains the stretch of Highway 407 from Burlington to Brougham under a lease from the Government of Ontario until the year 2098
 * The 407 East Development Group (407 EDG) maintains stretch of Highway 407 from 407 ETR to Harmony Road and Highway 412
 * Blackbird Infrastructure Group maintains stretch of Highway 407 from Harmony Road to Highway 115 and Highway 418
 * The Windsor Essex Mobility Group (WEMG) maintains the Herb Gray Parkway, the stretch of Highway 401 connecting to the future Gordie Howe International Bridge through Windsor, Ontario

Area term contracts (ATCs) are the latest maintenance and construction alternative being reviewed by the MTO. ATCs, if they are approved for tender, will cover all maintenance operations now performed by AMC contractors, but will also include annual pavement maintenance and replacement work, bridge rehabilitation, minor capital construction programs and corridor management.

Highway Carrier Safety and Enforcement
While policing on most MTO-managed roads is provided by the Ontario Provincial Police, certain law enforcement functions are provided by MTO Transportation Enforcement Officers and Ministry of Environment Emissions Enforcement Officers.

Ministry of Transportation Enforcement Officers (TEOs) enforce a variety of provincial highway safety legislation specific to operators of commercial vehicles. Driver hours of service, cargo securement, dangerous goods transportation, weights and dimensions, and vehicle maintenance and roadworthiness are the predominant focus of TEO inspection activities. Ontario's Highway Traffic Act, its regulations, the Compulsory Automobile Insurance Act, and the Dangerous Goods Transportation Act are core pieces of legislation from which TEOs derive their enforcement authorities. TEOs conduct commercial vehicle inspections using a standardized procedure established by the Commercial Vehicle Safety Alliance (CVSA).

Transportation Enforcement Officers inspect commercial vehicles, their loads, and driver's qualifications and documentation. They collect evidence, issue provincial offence notices or summons to court for violations, and testify in court.

Transportation Enforcement Officer deployment ranges from highway patrol and Truck Inspection Station (TIS) duties, audits of commercial vehicle operators, inspection and monitoring of bus and motor-coach operators, and the licensing and monitoring of Motor Vehicle Inspection Stations. Blitz-style joint force operations are periodically conducted in concert with provincial and municipal police.

Although many Transportation Enforcement Officers are licensed vehicle mechanics, most are not. TEOs hail from various backgrounds including driver licensing examination, automobile repair, commercial truck driving and other law enforcement agencies.

Offices
MTO's headquarters are located on three campuses:

 * Garden City Tower, St. Catharines, Ontario - 301 St. Paul Street
 * Downsview Complex, Toronto, Ontario - 87, 125, 145, and 159 Sir William Hearst Avenue
 * Ferguson Block, Toronto, Ontario - 77 Wellesley Street West

There are five regional offices:
 * Eastern - Kingston, Ontario
 * Central (Downsview) - Toronto, Ontario
 * Northwestern - Thunder Bay, Ontario
 * Southwestern - London, Ontario
 * Northeastern - North Bay, Ontario

Area offices are located in:

 * Bancroft, Ontario
 * North Bay, Ontario
 * Chatham, Ontario
 * Ottawa, Ontario
 * Owen Sound, Ontario
 * Cochrane, Ontario
 * Port Hope, Ontario
 * Huntsville, Ontario
 * Kenora, Ontario
 * Sault Ste. Marie, Ontario
 * Kingston, Ontario
 * London, Ontario
 * Sudbury, Ontario
 * Thunder Bay, Ontario
 * New Liskeard, Ontario

title: Ministry of Transportation of Ontario


text:
User:MyNameIsClare

I am a PhD student at the University of Plymouth, studying physical oceanography.

Pages I have started

 * Student_Action_For_Refugees_%28STAR%29
 * Refugee Council (UK)
 * Convention_Relating_to_the_Status_of_Refugees
 * List_of_famous_refugees

As you can see I am interested in refugee and asylum seeker issues, though I am by no means an expert

Useful (to me at least) links

 * Watchlist
 * Spanish Translation of the Week
 * Missing Encyclopedic Articles
 * UK Portal
 * Mind Benders
 * Templates
 * My skin which was copied from Ævar Arnfjörð Bjarmason's skin but without the part that moved the user menu

es:Usuario:MyNameIsClare

title: User:MyNameIsClare


text:
Collaroy, New South Wales

Collaroy is a suburb in northern Sydney, in the state of New South Wales, Australia. Collaroy is 22 kilometres north-east of the Sydney central business district, in the local government area of Northern Beaches Council. It is part of the Northern Beaches region. Nicknamed "The Roy" by many of the locals.

History
This area was originally part of Narrabeen but was renamed after the S.S. Collaroy ran aground on the beach in 1881. It was refloated and later wrecked on the Californian coast in 1889. Most of Collaroy's development has occurred since the mid twentieth century.

An anchor from the S.S. Collaroy has been on display on the grounds of Narrabeen Lakes Public School since 1928.

Collaroy Beach Post Office opened on 12 February 1923. Collaroy Plateau Post Office opened on 1 April 1949 and closed in 1988. Collaroy Plateau West Post Office opened on 1 November 1967 and was renamed Collaroy Plateau in 1996.

The beach and housing near the beach on Pittwater Road were badly affected by weather in early June 2016. A strip of houses lost backyards and were left in danger of collapse.

Landmarks
Collaroy's surf beach joins Narrabeen Beach at Wetherill Street making one continuous 3.4 km surf beach. Four Surf Lifesaving Clubs provide swimming supervision/surf rescue services (North Narrabeen SLC, Narrabeen SLC, South Narrabeen SLC, and Collaroy SLC).

Collaroy is home to one of the Salvation Army's largest conference and outdoor education centres in the area. The centre caters for many conferences of the Salvation Army as well as other churches, schools, community groups and businesses. It can cater for up to 440 people and has fully catered camp programs.

Demographics
According to the 2016 census, there were 7,870 residents in Collaroy. The most common ancestries were English 27.9%, Australian 23.7%, Irish 9.7%, Scottish 7.5% and Italian 4.8%. 68.8% of people were born in Australia. The next most common countries of birth were England 6.1% and New Zealand 2.1%. 80.8% of people spoke only English at home. Other languages spoken at home included Italian 1.7% and Portuguese 1.5%. The most common responses for religion were No Religion 31.2%, Catholic 27.5% and Anglican 17.4%.

Commercial area
Collaroy's shopping precinct is centred along Pittwater Road, which runs north–south through the suburb. Small retail businesses include cafes, restaurants, a book shop, takeaway bars, a pharmacy, a newsagent/post office, several hairdressers, a day spa, a YHA youth hostel, real estate agents, Collaroy cinema, the Collaroy Services club (also known as "The Beach Club") and "The Collaroy", which was formerly known as the Surf Rock Hotel, re-opened in November 2014.

Transport
Collaroy's public transport consists of buses operated by Keolis Downer Northern Beaches south through to the CBD, Manly, North Sydney (peak hour services only), and north to the suburbs from Narrabeen to Palm Beach.

Governance
Collaroy is in the federal seat of Mackellar. The seat is currently held by Independent politician Sophie Scamps, who defeated Jason Falinski of the Liberal Party at the 2022 Australian federal election. The seat had previously been held continuously by the Liberal Party since its creation in 1949.

Collaroy is in the NSW state electorate of Wakehurst, a seat held by Michael Regan.

Wildlife
Collaroy/Narrabeen is frequented by diverse bird and aquatic animal life including Sea Eagles, Pelicans, Terns, Ducks, Yellow-crested Cockatoo. Dolphins and whales can be seen during migrating season. In 2005 a young New Zealand Fur Seal was discovered washed up on the beach. Exhausted but alive, the Seal was nursed back to health by wildlife officers and then released. A similar incident, with another New Zealand fur seal coming ashore, occurred in August 2014.

Schools

 * The Pittwater House Schools

Notable people

 * Iza Coghlan, doctor
 * Gabriella Da Silva-Fick, tennis player
 * Tim Freedman, musician
 * Michael Hooper, rugby union player
 * Emma Jeffcoat, triathlete
 * Simon Kennewell, rugby union player
 * Boyd Killingworth, rugby union player
 * Johanna Konta, tennis player
 * Nat Young, surfer

title: Collaroy, New South Wales


text:
Wikipedia:Articles for deletion/Gainclone

 This page is an archive of the discussion about the proposed deletion of the article below. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was delete. Mindspillage (spill yours?) 06:58, 27 Apr 2005 (UTC)

Gainclone
An article about a piece of not that notable DIY audio equipment. -- Egil 12:37, 14 Apr 2005 (UTC)
 * Delete Vegaswikian 06:07, 15 Apr 2005 (UTC)
 * This page is now preserved as an archive of the debate and, like some other VfD subpages, is no longer 'live'. Subsequent comments on the issue, the deletion, or the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.


text:
Naji Hakim

Naji Subhy Paul Irénée Hakim (Arabic: ناجي صبحي حكيم [Naji Sobhi Hakim]; born 31 October 1955) is a Franco-Lebanese organist, composer, and improviser.

He studied the organ under Jean Langlais at the Conservatoire de Paris, and succeeded Olivier Messiaen as titular organist at the Église de la Sainte-Trinité, Paris, holding this position from 1993 to 2008. Before this, he was titular organist at the Sacré-Cœur basilica in the same city from 1985 to 1993, succeeding Daniel Roth.

Hakim's numerous improvisations and compositions for organ, orchestra, and other instruments have received renown. His works have been published by Schott Music, UMP, Combre, Éditions Alphonse Leduc, ABRSM, Fitzsimons, Éditions Gérard Billaudot, and American Carillon.

Youth: 1955–1972
Naji Subhy Paul Irénée Hakim was born into a Catholic family on 31 October 1955 in Beirut, Lebanon; to a businessman father, Subhy (died 2022), and his wife Katy Hakim. His Christian name is Paul.

His family were music-loving: his father played the mandolin and sang; his mother is an amateur pianist, and he and his three siblings also studied a variety of instruments of different types. Before the organ, Hakim studied the cello.

When he was five, he heard a pipe organ in his school, the Collège du Sacré-Coeur of Beirut. The instrument was built by Debierre-Gloton. Impressed by its sound, Hakim asked his mother two years later to get him a piano, to which she obliged. From then on, Hakim received his first piano lessons from his mother, who self-taught.

His brother, Amine, noticed the then-9 year old Hakim's enthusiasm for the organ and helped him break into the organ loft at the college. Naji was able to pull out all of the organ's stops before playing a single note. Frightened by the sound, the two brothers ran away. The school director took notice of the incident and ordered for the loft to be re-secured.

Hakim, who received permission to practise for half an hour every week (and later received unlimited access to the organ loft, chapel, and campus of the school for practising, under the consent of a new director), then taught himself the organ by using the method books of Jacques-Nicolas Lemmens, Harold Gleason and Marcel Dupré. He would later give his first recital in this chapel aged 15. A year later, he would later master the third of Dupré's Trois préludes et fugues, op. 7, and César Franck's First Chorale in E major.

Studies: 1972–1980
Many had noticed the young man's prodigiousness in the organ and talent for music, however, due to the prompting of his father, Hakim, aged 16, entered the Ecole Supérieure d'Ingénieurs de Beyrouth in 1972. He was advised that a musical career in Lebanon would have not been suitable by the present circumstances. The outbreak of the Lebanese Civil War in 1975, which caused the closure of his engineering school, forced him to flee to Paris in autumn of that year, where he completed his studies at Télécom in 1977.

He also took up a position as substitute organist at Sainte-Odile in Paris and prepared to enter the Conservatoire de Paris, failing the entrance examinations in 1976. Hakim then met Jean Langlais (1907–1991), organist of Sainte-Clotilde and an esteemed composer and organist, and began private lessons in organ playing and improvisation with him in a relationship that lasted about ten years. With his newfound friendship and encouragement, he was able to enter the conservatoire the following year; where he obtained seven first prizes in organ performance, organ improvisation, harmony, counterpoint, fugue, analysis, and orchestration.

Hakim was in the classes of Rolande Falcinelli (organ and improvisation), Roger Boutry (harmony), Jean-Claude Henry (counterpoint), Marcel Bitsch (fugue), Jacques Castérède (analysis) and Serge Nigg (orchestration); as well as that of Langlais himself (organ).

Professional career: 1980–2019
He was appointed as titular organist of the Basilique du Sacré-Cœur, Paris in 1985, succeeding Daniel Roth. He left in 1993 when he succeeded Olivier Messiaen after the latter's death at the Église de la Sainte-Trinité, Paris, from 1993 until 2008. He serves as Professor of Musical Analysis at the Conservatoire National de Région de Boulogne-Billancourt, and visiting professor of organ, improvisation, analysis, and composition at the Royal Academy of Music, London.

Hakim's compositional output includes instrumental music, symphonic music, and choral music. His works for the organ includes more than three dozen solo pieces, a number of works for organ and other instruments, and four organ concertos with orchestra.

Present day: 2019–
Despite retiring from the academic scene, Hakim remains an active professional concert organist today.

Awards
Hakim has won many awards for performance, improvisation, and composition. For example, his Symphonie en trois mouvements won the composition prize of the "Amis de l'Orgue" in 1984. The Embrace of Fire won first prize in 1986 in the International Organ Competition in memory of Anton Heiller, at Southern Missionary College in Collegedale, Tennessee. In addition, he was awarded the Prix de Composition Musicale André Caplet from the Académie des Beaux Arts in 1991. He has also been the recipient of prizes at the International Organ Competitions held in Beauvaiss (1981), Haarlem (1982), Lyon, Nuremberg, St. Albans (1983) (where he has since served on the jury), Chartres (1984), Strasbourg, and Rennes.

 * 2002: Honorary doctorate from the Holy Spirit University of Kaslik, Lebanon
 * 2007: Pope Benedict XVI conferred on him the "Pro Ecclesia et Pontifice" medal

Personal life
He currently lives in Bayonne with his wife Marie-Bernadette Dufourcet (who he married in 1980), annually visits his homeland of Lebanon, and composes regularly.

They have two children, Jean-Paul, who has followed in his footsteps as a composer, and Katia-Sofia, a musicologist and poet.

Hakim is a polyglot and speaks six languages: French, Arabic, English, Basque, Spanish, and German.

Music
Hakim began composing in 1983.

Organ solo

 * Cosmogonie (composed 1983. Unpublished.)
 * Petite suite (composed 1983. Waltham Abbey, Essex: UMP, 2004)
 * Symphonie en Trois Mouvements (composed 1984. Paris: Combre, 1984)
 * The Embrace of Fire: Triptyque (composed 1986. Paris: Combre, 1986)
 * Hommage à Igor Stravinsky. Triptyque (composed 1986. Paris: Leduc, 1990)
 * Expressions (composed 1988. Chicago, Illinois (USA): H. T. FitzSimons, 1988)
 * Memor (composed 1989. London: UMP, 1990)
 * Rubaiyat (composed 1990. London: UMP, 1991)
 * Variations on two themes: "Old hundredth" & "Donne secours" (composed 1991. London: UMP, 1991)
 * Rhapsody for organ duo (composed 1992. Waltham Abbey, Essex: UMP, 2005)
 * Mariales (composed 1993. London: UMP, 1993)
 * Incantation
 * Pastorale
 * Antienne
 * Hymne
 * Danse
 * Le Tombeau d'Olivier Messiaen: Trois Méditations symphoniques (composed 1993. London: UMP, 1994)
 * Vexilla regis prodeunt (composed 1994. Paris: Leduc, 1995)
 * Canticum (composed 1995. London: UMP, 1996)
 * Sinfonia in honore Sancti Ioannis Baptistæ (composed 1996. London: UMP, 1997)
 * Pange lingua (composed 1996. Paris: Leduc, 1997)
 * Pange lingua
 * Nobis datus
 * In supremœ nocte cœnœ
 * Verbum caro
 * Tantum ergo
 * Genitori, genitoque
 * Te Deum (composed 1997. London: UMP, 1998)
 * Bagatelle (composed 1997. London: UMP, 1998)
 * Chant de Joie (composed 1997. London: UMP, 1998)
 * The Last Judgment (composed 1999. Paris, Leduc, 2000)
 * Quatre Études-Caprices for pedal solo (composed 2000. Paris: Leduc, 2001)
 * Gershwinesca (composed 2000. Mainz: Schott, 2008)
 * In Organo, Chordis et Choro (composed 2001. Paris. Leduc, 2002)
 * Le Bien-aimé: Suite symphonique (composed 2001. Paris: Leduc, 2002)
 * 1. J'ai trouvé celui que mon cœur aime
 * 2. Notre joie et notre allégresse
 * 3. Viens, mon Bien-Aimé
 * 4. Avant que souffle la brise du jour
 * 5. Son aspect est celui du Liban, sans rival, comme les cèdres
 * 6. Ses traits sont des traits de feu
 * 7. Voici qu'il arrive sautant sur les montagnes, bondissant sur les collines
 * Ouverture Libanaise (composed 2001. Paris: Leduc, 2004)
 * Agapê (composed 2001. London: UMP, 2002)
 * Bach'orama: Organ Fantasia on themes by Johann Sebastian Bach (composed 2003. Paris, Leduc, 2004)
 * Gregoriana (composed 2003. Paris: Leduc, 2004)
 * Salve Regina (composed 2004. Mainz: Schott, 2005)
 * Sakskøbing præludier (composed 2005. Paris: Combre, 2006)
 * 1. Mit hjerte altid vanker (Always my heart wanders to the birth place of Jesus)
 * 2. Nærmere, Gud, til dig (Nearer, my God, to Thee)
 * 3. O Gud, du ved og kender (O God, Thou knowest)
 * 4. At sige verden ret farvel (The last farewell to life on earth)
 * 5. Hil dig, Frelser og Forsoner! (Hail You, Saviour and Atoner)
 * 6. Den mørke nat forgangen er (The gloomy night to morning yields)
 * 7. Nu blomstertiden kommer (Now the flowers are blooming)
 * 8. Påskeblomst! (Paschal Flow'r! why do you care to come forth?)
 * 9. Op, al den ting, som Gud har gjort (Arise, all things that God has made)
 * 10. O kristelighed! (O thou, image of Christ!)
 * 11. Så vældigt det mødte os først i vor dåb (How wonderful, that the Word first met us in baptism)
 * 12. Befal du dine veje (Commit thy way [unto God])
 * Mit seinem Geist: Variations on "Ein feste Burg" (composed 2006. Mainz: Schott, 2007)
 * AALAIKI'SSALAAM: Variations on a Lebanese theme (composed 2006. Mainz: Schott, 2007)
 * Esquisses Grégoriennes en forme de Messe basse (composed 2006. Mainz: Schott, 2007)
 * 1. Nos autem (Entrée)
 * 2. Ave maris stella (Offertoire)
 * 3. Pater noster (Élévation)
 * 4. Ave verum (Communion)
 * 5. O filii et filiae (Sortie)
 * Hommage à Jean Langlais (composed 2006. Mainz: Schott, 2008)
 * Glenalmond Suite (composed 2007. Waltham Abbey, Essex: UMP, 2007)
 * 1. Strømmende
 * 2. Favnende
 * 3. Smilende
 * 4. Jublende
 * To call my true love to my dance (composed 2007. Mainz: Schott, 2009)
 * 1. Theme
 * 2. Cantabile
 * 3. Valse
 * 4. Deciso
 * 5. Arabesque
 * 6. Burletta
 * 7. Tango
 * 8. Scherzando
 * 9. Berceuse
 * 10. Finale
 * All my founts shall be within you (Alle mine kilder skal være hos dig) (composed 2007. Mainz: Schott, 2009)
 * Ich liebe die farbenreiche Welt (Jeg elsker den brogede verden/I Love The Colourful World) (composed 2008. Mainz: Schott, 2009):
 * 1. Präludium
 * 2. Tanz-Toccata
 * Arabesques (composed 2009. Unpublished.):
 * 1. Prélude
 * 2. Pastorale
 * 3. Libanaise
 * 4. Arabesque
 * 5. Litanie
 * 6. Rondeau
 * Amazing Grace for organ (and soprano ad libitum) (composed 2009. Unpublished.)
 * Ein Haus voll Glorie schauet, variations on the hymn "Ein Haus voll Glorie schauet", 2017

Organ with other instruments

 * Old Hundredth for brass and organ (composed 1983. Paris: Leduc, 1995)
 * Fantaisie sur "Adeste, Fideles" with 2nd organ ad libitum (composed 1986. Paris: Bornemann/Leduc, 1988)
 * Duo Concertant for organ and piano (or two pianos) (composed 1988. London: UMP, 1990)
 * Rondo for Christmas for trumpet and organ (composed 1988. London: UMP, 1990)
 * Hymne au Sacré-Cœur for 7 trumpets and organ (composed 1992. Paris: Leduc, 1995)
 * Sonate for trumpet and organ (composed 1994. London: UMP, 1995)
 * Suite Rhapsodique for horn and organ (composed 2002. London: UMP, 2002)
 * Capriccio for violin and organ (composed 2005. London: UMP, 2005)
 * Variations on "Wie schön leuchtet der Morgenstern" for oboe and organ (composed 2008. Mainz: Schott, 2009)
 * Sindbad, Fantasy on Omani Popular Songs (Composed following a visit to Oman, 2014)

Orchestral and concertos

 * Fantaisie Celtique for piano and orchestra (composed 1985. London: UMP, 1997)
 * Concerto for organ and strings (composed 1988. London: UMP)
 * Les Noces de l'Agneau: Trois tableaux symphoniques for orchestra (composed 1996. London: UMP, 1997)
 * Hymne de l'Univers for orchestra (composed 1997. London: UMP, 1998)
 * Seattle Concerto for organ and orchestra (composed 2000. London: UMP, 2000)
 * Concerto for violin and orchestra (composed 2002. Paris: Leduc)
 * Concerto No. 3 for organ and string orchestra (composed 2003. London: UMP)
 * Ouverture Libanaise for orchestra (composed 2004. Paris: Leduc, 2004)
 * Sakskøbing præludier for chamber ensemble (flute, clarinet, bassoon, harp, violin, viola, and cello) (composed 2005. Paris: Combre, 2006)
 * 1. Mit hjerte altid vanker (Always my heart wanders to the birth place of Jesus)
 * 2. Nærmere, Gud, til dig (Nearer, my God, to Thee)
 * 3. O Gud, du ved og kender (O God, Thou knowest)
 * 4. At sige verden ret farvel (The last farewell to life on earth)
 * 5. Hil dig, Frelser og Forsoner! (Hail You, Saviour and Atoner)
 * 6. Den mørke nat forgangen er (The gloomy night to morning yields)
 * 7. Nu blomstertiden kommer (Now the flowers are blooming)
 * 8. Påskeblomst! (Paschal Flow'r! why do you care to come forth?)
 * 9. Op, al den ting, som Gud har gjort (Arise, all things that God has made)
 * 10. O kristelighed! (O thou, image of Christ!)
 * 11. Så vældigt det mødte os først i vor dåb (How wonderful, that the Word first met us in baptism)
 * 12. Befal du dine veje (Commit thy way [unto God])
 * Påskeblomst for string orchestra (composed 2005. Waltham Abbey, Essex: UMP)
 * Concerto No. 4 for organ and chamber ensemble "Det strømmende og uudslukkelige..." (composed 2007. Paris: Combre)

Other instruments and chamber music

 * Prélude et Fugue for bassoon quartet (composed 1983. London: UMP)
 * Shasta: Suite for harpsichord (composed 1986. Cleveland, Ohio (USA): Ludwig Music 1988)
 * Divertimento for guitar quartet (composed 1987. London: UMP)
 * Jeu for harp solo (composed 1987. Paris: G. Billaudot, 1990)
 * Sonate for violin solo (composed 1994. Paris: Leduc, 1996)
 * Caprice en Rondeau for flute and piano (composed 1998. Paris: Leduc, 1999)
 * Sonate for violin and piano (composed 2000. Paris: Leduc, 2002)
 * Dumia for piano solo (composed 2001. London: Associated Board of the Royal Schools of Music, 2001)
 * Ouverture Libanaise for piano solo (composed 2001. Paris: Leduc, 2004)
 * Påskeblomst for string quartet (composed 2007. Waltham Abbey, Essex: UMP)
 * Kammerconcert "Solen skinner altid på Beirut" for flute, clarinet, bassoon, harp, piano, violin, viola and cello (composed 2008. Paris: Leduc
 * AALAIKI'SSALAAM: Variations on a Lebanese theme for piano solo (composed 2006. Paris: Leduc, 2009)
 * Glenalmond Suite for piano solo (composed 2007. Waltham Abbey, Essex: UMP, 2009)
 * 1. Strømmende
 * 2. Favnende
 * 3. Smilende
 * 4. Jublende
 * Hymne til Alberto Giacomettis Kvinde på Kærre for carillon (composed 2009. Unpublished.)

Vocal works

 * Saul de Tarse: Oratorio for choir, soloists and orchestra (composed 1991. Paris: Leduc, 2000)
 * Missa resurrectionis for soprano solo (composed 1994. London: UMP, 1995)
 * Missa redemptionis for SATB choir a capella (composed 1995. London: UMP, 1995)
 * Phèdre: Cantata for mezzo-soprano and piano (composed 1997. London: UMP, 1998)
 * Children for SATB choir a capella (composed 1999. London: UMP, 1999)
 * Messe Solennelle for choir and organ (with 2nd organ ad libitum) (composed 1999. London: UMP, 1999)
 * Magnificat for soprano, violin and organ (composed 1999. Paris: Leduc, 2002)
 * Gloria for choir and organ (composed 2002. London: UMP, 2002)
 * Ave maris stella for choir and organ (composed 2003. London: UMP, 2003)
 * Phèdre for mezzo-soprano and orchestra (composed 2004. London: UMP)
 * The Dove for tenor and string quartet (composed 2005. Mainz: Schott, 2006)
 * The Dove for tenor (or soprano) and organ (composed 2005. Mainz: Schott, 2006)
 * The Dove for tenor and string orchestra (composed 2005. Mainz: Schott, 2005)
 * Jesu Redemptor omnium for choir, brass quintet, timpani and percussion (composed 2005. London: UMP)
 * Det strømmende: Canon (composed 2005. Unpublished.)
 * Magnificat for three treble voices and organ (composed 2006. Mainz: Schott, 2008)
 * Nunc dimittis for three treble voices and organ (composed 2006. Mainz: Schott, 2008)
 * Magnificat for soprano and organ (composed 2006. Mainz: Schott, 2008)
 * Verbum caro factum est for three treble voices and organ (composed 2007. Mainz: Schott, 2008)
 * The Angel Cried (Megalynarion of Pascha) for SATB choir and congregation (composed 2007. Mainz: Schott, 2008)
 * Set Me As A Seal Upon Your Heart (Læg mig som en seglring ved dit hjerte) for SATB choir a cappella (composed 2008. Mainz: Schott, 2009)
 * Amazing Grace for soprano (ad libitum) and organ (composed 2009. Unpublished.)

Discography

 * Naji Hakim plays Naji Hakim, Signum Records. ,
 * Naji Hakim : Seattle Concerto for organ, Marie-Bernadette Dufourcet, organ ; Seattle Symphony Orchestra dir. Gerard Schwarz, Ifo Records.
 * Naji Hakim : Piano works, Nicolas Chevereau, piano, Rejoyce Classique.

title: Naji Hakim


text:
User talk:Simin607607

Hate sam luv gab as di di lah

wana make frens?

title: User talk:Simin607607


text:
Jeanne Coyne

Jeanne Coyne (February 28, 1923 – May 10, 1973) was an American Broadway dancer, choreographer and actress.

Biography
With Carol Haney (1924 – 1964), Coyne assisted directors Stanley Donen and Gene Kelly, both of whom she married. She appeared as a dancer in the MGM films Words and Music, On the Town, Summer Stock, Singin' in the Rain and Kiss Me Kate.

She was married to Donen from 1948 to 1951, and to Kelly from 1960 to 1973. She and Kelly had two children, Timothy and Bridget.

She died on May 10, 1973, in Los Angeles, California, from leukemia, at the age of 50.

title: Jeanne Coyne


text:
Derafsh Kaviani

Derafsh Kaviani was the legendary royal standard Derafsh (in Latin: vexilloid) of Iran (Persia) used since ancient times until the fall of the Sasanian Empire. The banner was also sometimes called the "Standard of Jamshid" ( درفش جمشید), the "Standard of Fereydun" ( درفش فریدون) and the "Royal Standard" ( درفش کیی).

Meaning and origins
The name Drafš-e Kāvīān means "the standard of the kay(s)" (i.e., "kings", kias, kavis ) or "of Kāva." The latter meaning is an identification with an Iranian legend in which the Derafš-e Kāvīān was the standard of a mythological Iranian blacksmith-turned-hero named Kaveh, who led a popular uprising against the foreign demon-like ruler Zahhak. Recalling the legend, the 10th-century epic Shahnameh recasts Zahhak as an evil and tyrannical ruler, against whom Kaveh called the people to arms, using his leather blacksmith apron as a standard, with a spear as its hoist. In the story, after the war that called for the kingship of Fereydun had been won, the people decorated the apron with jewels and the flag became the symbol of Iranian nationalism and resistance against foreign tyranny. The symbol of Derafsh Kaviani is a lotus flower, which refers to the royal stars of Persia, and its history goes back to ancient Iranian beliefs from the Achaemenid Empire period.

Sasanian standard
By the late Sasanian era (224–651), a real Drafš e Kāvīān had emerged as the standard of the Sasanian dynasties. It was representative of the Sasanian state—Ērānšāhr (or "Iranian Empire"). Eran Shahr means Aryan Empire in Middle Persian—and may so be considered to have been the first "national flag" of Iran. The banner consisted of a Lotus on a purple field, was encrusted with jewels and had trailing red, gold and purple streamers on its edges. The term achtar was significant since the star also represented "fortune", and the capture and destruction of the banner on a field of battle implied the loss of the battle (and hence the loss of fortune). Following the defeat of the Sasanians at the Battle of al-Qādisiyyah, the Sasanian standard was recovered by one Zerar bin Kattab, who received 30,000 dinars for it. After the jewels were removed, Caliph Umar is said to have burned the standard.

As the symbol of the Sasanian state, the Drafsh e Kavian was irrevocably tied to the concept of Eranshahr and hence with the concept of Iranian nationhood. Thus, in 867, when Ya'qub-i Laith of the Saffarid dynasty claimed the inheritance of the kings of Persia and sought "to revive their glory," a poem written on his behalf sent to the Abbasid caliph said: "With me is the Drafsh e Kavian, through which I hope to rule the nations." Although no evidence that Ya'qub-i Laith ever recreated such a flag, star imagery in banners remained popular until the ascendance of the Lion and Sun symbol (after 1846).

Standard of the president of Tajikistan
The standard of the president of Tajikistan was introduced in 2006, on the occasion of the inauguration ceremony for the third term of Emomali Rahmon as head of state. It uses the same tricolour, charged with a depiction of the Derafsh Kāviān, the Sasanian royal standard; inside the Derafsh Kāviān is a depiction of a winged lion against a blue sky under a smaller representation of the crown and seven stars.

title: Derafsh Kaviani


text:
Lyuberetsky District

Lyuberetsky District (Любере́цкий райо́н) is an administrative and municipal district (raion), one of the thirty-six in Moscow Oblast, Russia. It is located in the central part of the oblast east of the federal city of Moscow. The area of the district is 122.31 km2. Its administrative center is the city of Lyubertsy. Population: 265,113 (2010 Census); The population of Lyubertsy accounts for 65.1% of the district's total population.

title: Lyuberetsky District


text:
Scuderia Centro Sud

Scuderia Centro Sud was a privateer racing team founded in Modena by Guglielmo "Mimmo" Dei and active in Formula One and sports car racing between 1956 and 1965.

Dei had been an amateur driver in the 1930s. In the early 1950s he opened a Maserati dealership in Rome. Keen on maintaining a relationship with motorsport, in 1956 he founded his own team. The name "Centro Sud" refers to the parts of Italy where his adoptive and native cities are (Modena and Rome).

Over the course of nine seasons, Scuderia Centro Sud entered a total of 49 World Championship rounds, with cars such as the Maserati 250F, various Maserati-powered Coopers and, in the 1960s, a BRM P57. After a very promising start (they scored their first points at their debut with Luigi Villoresi), Centro Sud went on to earn a further total of 24 points, mostly with Masten Gregory and Tony Maggs. But they never won a race: Gregory's third place at the 1957 Monaco Grand Prix was the team's best result.

Centro Sud was the only Italian racing team that took part in the Tasman races in Australia and New Zealand during the winter of 1961-1962.

One of their most notable feats was to be the first team in the history of Formula One to run a female driver, when Maria Teresa de Filippis (who had already raced as a privateer in the 1958 Belgian Grand Prix a few weeks earlier) competed in the 1958 Portuguese Grand Prix as a Centro Sud team driver. Future 1963 24 Hours of Le Mans) and 1967 24 Hours of Daytona winner Lorenzo Bandini made his Formula One debut with the team at the 1961 Belgian Grand Prix.

Complete Formula One World Championship results
(key) * After retiring his Scuderia Centro Sud-entered car, Shelby subsequently took over Masten Gregory's car, entered by Temple Buell, finishing fourth.

title: Scuderia Centro Sud


text:
User talk:Fxfxfx

I would like to make this a personal category for various thoughts - but don't know how to :-(

Thanks for experimenting with Wikipedia. Your test worked, and has now been reverted or removed. Please use Sandbox for any other tests you want to do, since testing in articles will be reverted quickly. Please see the welcome page if you would like to learn more about contributing to our encyclopedia. Thanks. Lupo 12:48, 14 Apr 2005 (UTC)

title: User talk:Fxfxfx


text:
Wikipedia:Articles for deletion/Kenneth Lacy

 This page is an archive of the discussion about the proposed deletion of the article below. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was delete. Mindspillage (spill yours?) 15:43, 24 Apr 2005 (UTC)

Kenneth Lacy
Vanity, borderline nonsense, created by User:206.211.68.242 who has been vandalizing today's Feature Article. Jpo 12:42, Apr 14, 2005 (UTC)
 * Speedy delete. Feydey 18:20, 14 Apr 2005 (UTC)
 * Delete. Swiftly. Phils 20:05, 14 Apr 2005 (UTC)
 * Delete, not notable, vanity. Megan1967 07:30, 15 Apr 2005 (UTC)
 * Delete speedily. I don't think it refers to the former CIO of UPS. Wmahan. 23:18, 2005 Apr 18 (UTC)
 * This page is now preserved as an archive of the debate and, like some other VfD subpages, is no longer 'live'. Subsequent comments on the issue, the deletion, or the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.


text:
Thursday (disambiguation)

Thursday is a day of the week.

Thursday may also refer to:

Film

 * Thursday (film), a 1998 film directed by Skip Woods
 * A Thursday, a 2022 Indian film directed by Behzad Khambata

Television

 * "Thursday" (13 Reasons Why), an episode of 13 Reasons Why

Fictional characters

 * Ruby Thursday, a fictional character in the Marvel Comics Universe
 * Thursday Next, a fictional character in novels by Jasper Fforde
 * Fred Thursday, a fictional character in the television series Endeavor
 * Thursday, a fictional mouse in four books by Michael Bond

Music

 * Thursday (band), an American post-hardcore band
 * Thursday (opera) (German: Donnerstag), an opera by Karlheinz Stockhausen from his Licht cycle

Albums

 * Thursday (album), mixtape or title track by the Weeknd

Songs

 * "Thursday", a song from the musical revue Blackbirds of 1939 written by Haber and Sachs
 * "Thursday" (Pet Shop Boys song), a song by the Pet Shop Boys
 * "Thursday", a song by Morphine from Cure for Pain and also used in the soundtrack to the film Beavis and Butt-head
 * "Thursday", a song by Country Joe and the Fish from I-Feel-Like-I'm-Fixin'-to-Die, 1967
 * "Thursday", a song by Jim Croce from I Got a Name, 1973
 * "Thursday", a song by The Puddle 1993
 * "Thursday", single by The Features 2000
 * "Thursday" (Jess Glynne song), 2018

Other uses

 * Thursday October Christian I (1790–1831), first son of Fletcher Christian (leader of the historical mutiny on HMS Bounty)
 * Thursday, West Virginia, a community in the United States
 * Abergavenny Thursdays F.C., a Welsh football club
 * Thursday Island, Queensland, Australia

title: Thursday (disambiguation)


text:
Brian Kilcline

Brian Kilcline (born 7 May 1962) is an English former professional footballer. He played as a centre half for Notts County, Coventry City, Oldham Athletic, Newcastle United, Swindon Town, Mansfield Town and Halifax Town, and was famous for his long hair and moustache.

Career
Kilcline captained Coventry City in the 1987 FA Cup Final at Wembley against Tottenham Hotspur. At the time it was thought that Kilcline was responsible for scoring an own goal to give Spurs a 2–1 lead in the 40th minute, but this goal was eventually credited to Gary Mabbutt. Kilcline and Mabbutt were to clash again in the second half when Kilcline brought down Mabbutt with a tackle. Kilcline was not cautioned by referee Neil Midgley but had to be replaced by substitute Graham Rodger just a minute before the end of normal time due to the injury he himself sustained in the clash. After Coventry's extra time winner (the match finished 3-2) Kilcline limped slowly up the Wembley steps to receive the trophy for the only time in Coventry's history.

In 1991, Kilcline joined newly promoted Oldham Athletic but his stay at the club was not to be a long one.

When Kevin Keegan became manager of Newcastle United in 1992, "Killer" Kilcline was his first signing, and was immediately installed as club captain. He became known for his hard tackling and aerial ability - he often would prefer a diving header to a volley, even for balls only half a metre off the ground. Keegan later remarked that Kilcline was "the most important signing" he had ever made for the club. This was echoed by fans, who considered him partially responsible for saving the club from relegation and possible bankruptcy.

During the 1993–94 season, he briefly played for Swindon Town in the Premier League.

Personal life
Kilcline has been married to Lynn since 1994. As of 2017, the couple split their time between homes in Portugal and Holmfirth, where they own a number of rental properties.

title: Brian Kilcline


text:
BBC 2W

BBC 2W was a digital television channel run by the BBC in Wales until January 2009. It replaced the standard BBC Two broadcast on digital services in Wales – running on weekdays from 8.30pm to 10pm. Launched on 5 November 2001, it had an initial reach of 1.1 million viewers.

History
It served as a replacement for BBC Choice Wales, which had been shut down on 30 March 2001. 2W broadcast in English and was aimed at the English-speaking population, unlike S4C, which broadcasts primarily in Welsh. The digital-only service was replaced with a single BBC Two for Wales on 2 January 2009. BBC 2W was designed to offer "a unique experience unavailable anywhere else with the watchwords of topicality and style, intelligence with an occasional touch of irreverence, shining through" for Welsh audiences.

The channel name on the Electronic Programme Guide was BBC 2W although outside its broadcast hours the channel was referred to onscreen as BBC Two Wales, using the BBC Two logo. The channel received complaints from some viewers because of its policy of broadcasting only Welsh-based programmes (including many repeats) during its opt-out hours; unlike BBC Two Wales which only opted out for live sport and new programming. The first switchoff of analogue television in the UK, for instance, was controversial because viewers in Llansteffan and Ferryside, whose analogue transmitter was due to be switched off, insisted that BBC Two Wales be left broadcasting in analogue.

The channel did provide a choice to all other viewers. Viewers on satellite could select a different BBC Two region (but not BBC Two Wales), and viewers on Freeview and cable could switch back to analogue to watch BBC Two Wales, although they were unable to watch the programme in widescreen.

Originally, the channel's news programme was 2W News & Sport, launching with the channel. In 2005, this was replaced by a bulletin of Wales Today, also shown on BBC One Wales. The bulletin, entitled Wales Today on 2W carried the same titles as that on BBC One Wales and was broadcast from the same studio with the same main presenters.

On-screen presentation
BBC 2W's original ident in 2001 was a bright green design with a stylised spinning cube that could transition directly into a programme menu. In 2003, a new set of idents debuted featuring a number of live action sequences where a green BBC 2W logo box is integrated into the scene as a physical object (such as on a beer tap or painted on a garage door), whilst still ending up in the bottom right-hand corner location like the usual BBC Two idents.

However from 18 February 2007, BBC 2W simply used the standard BBC Two idents with the 2W box. At crossover (when BBC Two Wales became BBC 2W) the boxes alternated between each other during the ident. This alternation also occurred during trailers which advertised programmes during BBC 2W hours.

Closure
BBC 2W closed down on 2 January 2009 in the run-up to digital switchover as part of plans to achieve 3% annual efficiencies at BBC Wales. Digital BBC Two in Wales reverted to the network version, with less frequent regional programmes as is the arrangement on Analogue BBC Two Wales.

title: BBC 2W


text:
Wikipedia:Wikipedia Signpost/2005-04-18/Template standardisation

In an effort to standardise the appearance of templates on article talk pages, a competition opened last week to come up with a basic visual design for them, ending a brief dispute over one of the affected templates.

The use of template messages has previously prompted concerns about them being misused and overused, with some past efforts trying to encourage placement of templates on talk pages where possible instead of directly on the article. Violet/Riga created a proposal at User talk:Violetriga/statusdevelopment to standardise the look of the current talk page templates throughout Wikipedia after realising they lacked consistent formatting. ALoan commented, "I think bringing some consistency to these templates is a fine idea".

Feeling that the combination of templates for some articles often made talk pages look messy, the proposal aimed to give them more of a table-like look. After some discussion and feedback, Violet/Riga went ahead and implemented this proposal, but an edit war developed focusing primarily on the featured template. This primarily involved Violet/Riga and JDG, who explained that he didn't like the layout used, claiming that the support for Violet/Riga's proposal was more for the concept of standardisation generally.

Turning it into a competition
At length it was suggested that a competition could be held to satisfy the opinions of both sides. Both editors agreed to this and the affected templates were restored to their previous state. Violet/Riga created a competition page at Template standardisation, which quickly received a number of submissions, some based on the existing templates and others derived from Violet/Riga's new design.

So far, nine different users have submitted a total of 17 designs for consideration. The competition is scheduled to close Sunday 24 April 2005 at 23:59 (UTC). At that point a public vote will be held to determine the favourite design.

Also this week: Editor's note — Dworkin scoop — Tax exemption — Search — Spoken articles — Encarta digs — Design contest — T.R.O.L.L. — Features and admins — Press coverage


text:
Raelene Boyle

Raelene Ann Boyle (born 24 June 1951) is an Australian retired athlete, who represented Australia at three Olympic Games as a sprinter, winning three silver medals, and was named one of 100 National Living Treasures by the National Trust of Australia in 1998. Boyle was diagnosed with breast cancer in 1996 and subsequently became a board member of Breast Cancer Network Australia (BCNA). In 2017, she was named a Legend in the Sport Australia Hall of Fame.

Early life
Boyle was born on 24 June 1951, the daughter of Gilbert and Irene Boyle, in Coburg, a suburb of Melbourne. She was educated at Coburg High School in Melbourne.

Sporting career
After strong performances in the 1968 Australian Championships and Olympic trials, Boyle was selected to represent Australia at the 1968 Summer Olympics in Mexico City, at the age of 16. At 17, she won a silver medal in the 200-metre sprint and placed 4th in the 100 metres. Setting world junior records in both distances, of 22.73 and 11.20 seconds. The 200-metre record lasted 12 years before being broken; the 100-metre 8 years.

Boyle competed in the 1970 British Commonwealth Games in Edinburgh, where she contributed to Australia's number one position on the medal tally with three gold medals, in the 100 and 200-metre sprints and the 4 × 100-metre relay.

At the 1972 Olympics in Munich, Boyle collected two more silver medals, in the 100-metre and 200-metre sprints. In both races, she came second to East German Renate Stecher.

In 1974, at the Christchurch British Commonwealth Games, Boyle duplicated her results at the Edinburgh Games, winning three more gold medals in the same three events. Breaking the games record in both the 100 metres 11.27 and 200 metres with a 22.50 clocking.

In January 1976, she and her team-mates beat an eight year old world record for the 4 × 200 metre relay in Brisbane.

At the 1976 Olympics in Montreal, Boyle finished fourth in the final of the 100-metre sprint, but was disqualified from the 200-metre-race for making two false starts. A video replay later showed that she had not false started on her first start. However, Boyle did receive the honour of acting as the flag bearer for the Australian team, the first woman to do so.

Boyle was unable to replicate her previous Commonwealth success at the 1978 Commonwealth Games in Edmonton, winning only a silver medal in the 100-metre sprint before withdrawing from the 200m and relay due to injury.

Boyle was selected to compete in the 1980 Olympics in Moscow but eventually withdrew from the team for what she stated were personal reasons, during the long dispute within Australian sporting circles over whether to join the USA led boycott of the Games.

Her final major competitive appearance was at the 1982 Commonwealth Games in Brisbane, where she won gold in the 400-metre sprint, and silver in the 4 × 400-metre relay.

Through her successful career, Boyle won seven gold and two silver medals at the Commonwealth Games, in addition to her three silver medals at the Olympic Games.

Many East German athletes were later revealed to have used anabolic steroids within a systematic state-sponsored doping program. Boyle has stated she believes that she would have won gold at the 1972 Olympics if not for drug use by her competitor. The IOC only banned the use of anabolic steroids in 1975.

Honours

 * 15 June 1974 – appointed a Member of the Order of the British Empire (MBE) for services to sport.
 * 1974 – awarded the ABC Sportsman of the Year Award
 * 1985 – inducted into the Sport Australia Hall of Fame.
 * 1991 – received an "award for excellence" in her sport, and for contributions to the Commonwealth Games by the Australian Commonwealth Games Association
 * 25 September 1989 – awarded the Douglas Wilkie Medal by the Anti-Football League, for doing the least for football in the best and fairest manner.
 * 2000 – Boyle pushed Betty Cuthbert in her wheelchair in the torch relay during the 2000 Sydney Olympics Opening Ceremony.
 * 2000 – awarded Australian Sports Medal.
 * 2001 – awarded Centenary Medal.
 * 2004 – inducted into the Athletics Australia Hall of Fame.
 * 2007 – appointed as a Member of the Order of Australia (AM) for service to the community through a range of roles with organisations that support people with cancer, particularly Breast Cancer Network Australia.
 * 2013 – named in Australia's Top 100 Sportswomen of All Time.
 * 2017 – upgraded to a Sport Australia Hall of Fame Legend.

Personal life
Boyle was diagnosed with cancer in 1996 and ovarian cancer in 2000 and 2001.

Boyle works to raise community awareness about breast cancer and has been a very active board member of Breast Cancer Network Australia (BCNA) since 1999.

Boyle currently lives on the Sunshine Coast in Queensland with her partner Judy Wild.

title: Raelene Boyle


text:
User talk:Jdeboer

AfD nomination of Woldemar (Peter) Petri
I have nominated Woldemar (Peter) Petri, an article you created, for deletion. I do not feel that this article satisfies Wikipedia's criteria for inclusion, and have explained why at Articles for deletion/Woldemar (Peter) Petri. Your opinions on the matter are welcome at that same discussion page; also, you are welcome to edit the article to address these concerns. Thank you for your time. TRAVELLINGCARI My storyTell me yours 05:58, 23 February 2008 (UTC)

Repost of Peter Petri
Hello, this is a message from an automated bot. A tag has been placed on Peter Petri, by another Wikipedia user, requesting that it be speedily deleted from Wikipedia. The tag claims that it should be speedily deleted because Peter Petri was previously deleted as a result of an articles for deletion (or another XfD) To contest the tagging and request that administrators wait before possibly deleting Peter Petri, please affix the template  to the page, and put a note on its talk page. If the article has already been deleted, see the advice and instructions at WP:WMD. Feel free to contact the bot operator if you have any questions about this or any problems with this bot, bearing in mind that '''this bot is only informing you of the nomination for speedy deletion; it does not perform any nominations or deletions itself. To see the user who deleted the page, click here''' CSDWarnBot (talk) 20:30, 7 March 2008 (UTC)

Bruce Reyes-Chow Photo
Hi Jdeboer,

I apologize for my late reply. I acquired the photo from Joseph Williams, a photographer for PC(USA). He gave me the photo, but I believe the photo belongs to Presbyterian Church (U.S.A.) How should I credit the photo, in this case? How should I acquire a release?

Thanks, Keithbrooks (talk)

ArbCom elections are now open!
MediaWiki message delivery (talk) 13:00, 23 November 2015 (UTC)

Nomination of Bruce Reyes-Chow for deletion
A discussion is taking place as to whether the article Bruce Reyes-Chow is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Articles for deletion/Bruce Reyes-Chow until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.

title: User talk:Jdeboer