Re:Hire a programmer. (Score 1)

I have read all advices, existing at 23.09.08, and i'd like to listen, how i should look at example of my projects, which i can't implement by own forces. E.g. SQL5 http://computer20.euro.ru/site/computer20/en/author/driven-scene_eng.htm http://sql50.euro.ru/site/sql50/en/author/resume_eng.htm http://sql50.euro.ru/sql5.16.4.pdf I made submissions in IBM, Microsoft, etc - they protect own already made investments. I informed community on [e-mail] http://www.google.com/custom?q=Dmitry+Turin&sa=Google+Search&cof=L%3Ahttp%3A%2F%2Fwww.xml.org%2Fxml%2Fimages%2Flogoheader.gif%3BAH%3Acenter%3BGL%3A0%3BS%3Ahttp%3A%2F%2Flists.xml.org%3BAWFID%3A1f6027004f263143%3B&domains=lists.xml.org&sitesearch=lists.xml.org I appeal in foreing (MIT, Chicago) and russian universities. Students can't even forces to implenent tickets like mentioned below. So all, what i archived, is publication in Ingres. http://blogs.ingres.com/technology/2008/07/31/new-step-in-office-technologies-driven-scene/ http://blogs.ingres.com/technology/2008/07/31/bringing-dbms-in-line-with-modern-communication-requirements-sql2009/ And what you can seggest me ??? --- Ticket "switching and showing dialect". Add following possibility into parser: after command SET SQL DIALECT 5; the following expressions SELECT a/@a1 ... ... WHERE b/@b1=5 ... ... FROM schemeÂtab ... UPDATE c SET @c1=5 ... DELETE * FROM ... CREATE PROCEDURE p ( @var1 type1, ... are interpreted similar to old dialect SELECT a.a1 ... ... WHERE b.b1=5 ... ... FROM scheme.tab ... UPDATE c SET c1=5 ... UPDATE c SET d/@d1=5 ... DELETE FROM ... CREATE PROCEDURE p ( var1 type1, ... and after command SET SQL DIALECT 4; it's occurs switching to old dialect. Implement command SHOW SQL DIALECT; returning values '4' and '5' depending on in what state parser is. Corresponding slides: #125. Help: commands 'SET SQL DIALECT' and 'SHOW SQL DIALECT' are implemented in DBMS 'InterBase', where they install and return values '1', '2', '3. --- Ticket "inexact names in request". Implement SQL-command SELECT ... WHERE field1~~field2; where '~~' designates counting of Levenshtein distance, and records are extracted in sorted kind in order of growth of this value (records with the least distance are issued first). Corresponding slides: #44-46. Help: calculation itself of Levenshtein distance is implemented in 'Postgres' by function 'levenshtein', so request mentioned above is similar to SELECT ... ORDER BY levenshtein(field1,field2);