AND 

mysql -u root -p

"mysql" не является внутренней или внешней командой, исполняемой программой или пакетный файлом.

identified by 'xyz'

{player, id, name}
{player_item, player_id, property_id, count}
{item, id, name}
{item_property, item_id, property_id, count}
{property, id, name, value}

threads = selectAllThreads
for t in threads:
    threadFiles = selectFiles t
    lastPosts = selectLastPosts t
    for p in lastPosts:
        lastPostFiles = selectFiles p
        ...

days_diff = (ts_paid - ts_billed) / (3600 * 24);  #timestamps
fee = sum_billed / 100;

if (days_diff < 10)
	billed -= (fee < 2) ? fee : 2;
elseif (days_difff > 20)
	billed += (fee < 1) ? fee : 1;

diff = paid - billed

dates = [(dtj(date(2013, 12, 31)), dtj(date(2014, 1, 4)))]

sum = sum - 2

sum = sum

SELECT * -- Ну или что там за поля нужны
FROM table1
WHERE t.num LIKE 'X' AND t.date>'DD.MM.YYYY' -- Условие взятое из поста анона
ORDER BY num

SELECT * 
FROM  table1
ORDER BY name

SELECT * 
FROM  table1 a
JOIN table1 b ON a.name = b.name

SELECT 
    t.num      AS num,                         -- столбик из первой таблицы
    COUNT(t.*) AS count,                       -- агрегирующая функция, работает вместе с "GROUP BY"
    s.type     AS type,                        -- столбик из второй таблицы
    s.date     AS date                         -- столбик из второй таблицы
FROM 
    table1 t                                   -- table1 имеет первичный ключ "id"
LEFT OUTER JOIN
    table2 s                                   -- table2 имеет первичный ключ "id", а ещё
ON
    t.id = s.item_id                           -- там у каждой записи "item_id" и это жжж неспроста
AND
    t.num LIKE 'X'                             -- условие внутри джойна
AND 
    t.date > 'DD.MM.YYYY'                      -- условие внутри джойна
GROUP BY 
    t.id                                       -- я не знаю зойчем у вас поле "num" когда есть ключи
HAVING 
    count > 1                                  -- условие после группировки
ORDER BY 
    count ASC                                  -- отсортируем, чтобы быстрее найти

prev_record = '';

foreach (records as record ) {
    if ( ... ) {
    } else {
    }

    prev_record = record
}

product.id
item.id
item.product_id

FROM
    product
LEFT OUTER JOIN
    item
ON
    product.id = item.product_id

CREATE ROLE postbackup LOGIN
    ENCRYPTED PASSWORD 'md58924e1371a70b427c0c2f0ccc34b31b5'
    NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE REPLICATION;

Таблица ITEMS:[ITEMS_PK, ITEM_SYMBOLIC (UNIQUE, но не ключ!), ITEM_PROPERTIES_FK (внешний ключ на таблицу ITEM_PROPERTIES)]
Таблица ITEM_PROPERTIES:[ITEM_PROPERTIES_RCRD_PK, HOLINESS_PROPERTY_FK, CONTAINER_PROPERTY_FK, IS_WEAPON, IS_HEADGEAR, IS_FOOTWEAR, IS_FOOD]
Таблица HOLINESS_PROPERTY:[HOLINESS_PROPERTY_ID, HOLINESS_AMOUNT]
Таблица CONTAINER_PROPERTY:[CONTAINER_PROPERTY_ID, CONTAINER_VALUE]

try:
	cnxn = pyodbc.connect('DRIVER={Microsoft Access Driver (*.mdb)};DBQ='+dbPath)
	cursor = cnxn.cursor()
	try:
		with open(csvPath) as csvfile:
			reader = csv.DictReader(csvfile)
			for row in reader:
				cursor.execute("INSERT INTO DatosTecnica (IdTecnica,Nombre,TipoMuestra,ConstituyenteAsociado,Unidades,\
				RangoReferencia,FechaSesion,IdRegistroTecnica,ValorBlanco,FechaBlanco,NumCalibradores,ValorCalibrador,\
				FechaCalibrador,FactorCalibracion,Exportada,TecCalculada,BorderLine) VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)",
				(row['IdTecnica'],row['Nombre'],int(row['TipoMuestra']),row['ConstituyenteAsociado'],row['Unidades'],
				row['RangoReferencia'],'{ts\''+datetime.strptime(row['FechaSesion'],'%m/%d/%y %H:%M:%S').strftime('%Y-%m-%d %H:%M:%S')+'\'}',
				long(row['IdRegistroTecnica']),float(row['ValorBlanco']),'{ts\''+datetime.strptime(row['FechaBlanco'],'%m/%d/%y %H:%M:%S').strftime('%Y-%m-%d %H:%M:%S')+'\'}',
				long(row['NumCalibradores']),row['ValorCalibrador'],'{ts\''+datetime.strptime(row['FechaCalibrador'],'%m/%d/%y %H:%M:%S').strftime('%Y-%m-%d %H:%M:%S')+'\'}',
				row['FactorCalibracion'],int(row['Exportada']),int(row['TecCalculada']),row['BorderLine']))
	except (pyodbc.DataError,pyodbc.ProgrammingError) as e:
		print unicode(str(e.args[1]),encoding='cp1251');
except (pyodbc.Error) as e:
	print unicode(str(e.args[1]),encoding='cp1251');
cursor.close()
cnxn.commit()
cnxn.close()

[HYC00] [Microsoft][Драйвер ODBC Microsoft Access]Дополнительная возможность не реализована  (106) (SQLBindParameter)

HY000 	All bound columns are read-only. 	There must be an updatable column to use SQLSetPos or SQLBulkOperations to change or insert a row.
HY000 	An old netlib (%s) has been detected. Please delete it and restart the application. 	The netlib that was being loaded was out of date. The driver requires a newer netlib.

The problem could be a netlib in the current directory of the application, which is being loaded instead of the one in the system directory, or it could be that the netlib was not installed properly or is corrupted. If the netlib specified in the error text exists elsewhere than in the Windows system directory, delete it. If the netlib exists only in the system directory, install the client utilities on the client and restart the application.
HY000 	Attempt to bulk-copy a NULL value into a Server column which does not accept NULL values. 	The field contains a NULL value, but the column does not allow NULL values.
HY000 	Attempt to bulk-copy an oversized column to the SQL Server. 	The length supplied for a column is larger than the column definition in the table.
HY000 	Attempt to read unknown version of BCP format file. 	The header line in the bcp format file was not a recognized version.
HY000 	Bad bulk-copy direction. Must be either IN or OUT. 	The bcp_init call did not specify a valid direction for the eDirection parameter.
HY000 	Bad terminator. 	The terminator string supplied in bcp_bind is invalid.
HY000 	Bcp host-files must contain at least one column. 	No columns were selected to be loaded.
HY000 	Cannot generate SSPI context. 	The driver could not obtain an SSPI context required for integrated security. The native error will contain the Win32 error code.
HY000 	Cannot initialize SSPI package. 	The driver could not obtain an SSPI context required for integrated security. The native error will contain the Win32 error code.
HY000 	Communication module is not valid. Driver has not been correctly installed. 	The network library .dll is corrupted. Install the client utilities on the client and restart the application.
HY000 	Connection is busy with results for another hstmt. 	The SQL Server ODBC driver allows only one active hstmt. For more information, see Using Default Result Sets.
HY000 	Connection is not enabled for BCP. 	The application using the BCP API must set the SQLSetConnectAttr or SQL_SS_COPT_BCP attribute before connecting.
HY000 	Failure during closing of connection. 	The ConnectionClose function in the network library failed. This problem is typically caused by a network or SQL Server problem.
HY000 	For BCP, all variable-length data must have either a length-prefix or a terminator specified. 	bcp_bind was called with SQL_VARYLEN_DATA, but neither a prefix length nor a terminator was specified.
HY000 	Host-file columns may be skipped only when copying into the server. 	A bcp out format file specified that a column should be skipped. This is not allowed. Either create a view containing only the desired columns and bcp out from that view, or use the -Q flag to provide a SELECT statement selecting only the desired columns.
HY000 	Incorrect host-column number found in BCP format-file. 	The format file contains a column number greater than the number of columns in the table.
HY000 	I/O error while reading bcp data-file. 	 
HY000 	I/O error while reading BCP format file. 	 
HY000 	I/O error while writing bcp data-file. 	 
HY000 	I/O error while writing bcp error-file. 	 
HY000 	Invalid option. 	The eOption parameter to bcp_control was not valid.
HY000 	Non-default parameter not allowed after default parameter. 	Parameters to a stored procedure cannot have a non-default value after any preceding parameter has been specified with the default value.
HY000 	Not enough columns bound. 	For a bcp out, not all columns of the table were bound. Either create a view which contains only the desired columns and bcp out from that view or, use the -Q flag to provide a SELECT statement selecting only the desired columns.
HY000 	ODBC BCP/Driver version mismatch. 	The Sqlsrv32.dll and Odbcbcp.dll .dlls do not have identical versions. Install the client utilities on the client and restart the application.
HY000 	Protocol error in TDS stream. 	The TDS stream from the server is invalid. This problem is typically caused by a SQL Server problem. Check the SQL Server error log.
HY000 	Table contains less rows than first row count. 	A starting row number was supplied, but the table on the server did not contain that number of rows. No rows were copied to the host-file.
HY000 	Table contains less rows than last row count. 	An ending row number was supplied, but the table on the server did not contain that number of rows.
HY000 	Table has no text/image columns. 	bcp_moretext was called, but the table does not contain any text or image columns.
HY000 	TDS buffer length too large. 	The TDS stream from the server is invalid. This problem is typically caused by a SQL Server problem. Check the SQL Server error log.
HY000 	Text column data incomplete. 	The summation of the lengths supplied by bcp_moretext did not match the length supplied in bcp_bind or bcp_collen.
HY000 	The BCP host-file contains less rows than first row count. 	A starting row number was supplied, but the host-file did not contain that number of rows. No rows were loaded.
HY000 	The row length exceeds SQL Server's maximum allowable size. 	The summation of the data lengths for a row is larger than the maximum row size.
HY000 	The stored procedure required to complete this operation could not be found on the server (they were supplied with SQL Server). Please contact your system administrator. 	Install the ODBC catalog stored procedures by executing \Msqql\Install\Instcat.sql.
HY000 	Unable to load communication module. Driver has not been correctly installed. 	The network library .dll specified for the connection does not exist on this client. Install the client utilities on the client and restart the application.
HY000 	Unable to open BCP host data-file. 	The file name specified in the bcp_init call does not exist or is opened by another application.
HY000 	Unable to open BCP error-file. 	The error file name specified in the bcp_init call does not exist or is opened by another application.
HY000 	Unable to read driver version. 	The driver was unable to read the version block in its .DLL. Install the client utilities on the client and restart the application.
HY000 	Unexpected EOF encountered in BCP data-file. 	During a bcp in operation, end-of-file was detected on the data file while in the middle of processing the last row. This is typically caused by having a different number of columns, types, nullability, or sizes between the original table and the table being loaded.
HY000 	Unicode conversion failed. 	An error occurred during conversion to or from a Unicode string. The native error will contain the Win32 error code.
HY000 	Unicode conversion failed. The code page of the SQL server must be installed on the client system. 	The server code page must exist on the client for proper operation. Either clear the Auto Translate check box for the DSN or install the code page of the server on the client. The server code page can be determined by running EXEC sp_server_info 18.
HY000 	Unknown token received from SQL Server. 	The TDS stream from the server is invalid. This error is typically caused by a problem on the server. Check the SQL Server error log.
HY000 	Warning: Partial insert/update. The insert/update of a text or image column(s) did not succeed. 	A failure during insertion or update of a text, image, or ntext column occurred. That column will not contain the proper data. Roll back the transaction, if possible.

Syntax error: Unexpected end of text, period sign expected.