wwwsqldesigner - Project Hosting on Google Code

Yesterday 44 hours ago issue 57 (fields needed) Status changed by ondrej.zara - Feel free to adjust your datatypes.xml as necessary :) Distribution version covers only the basic data types to provide maximum compatibility with other DB engines. Status: WontFix Feel free to adjust your datatypes.xml as necessary :) Distribution version covers only the basic data types to provide maximum compatibility with other DB engines. Status: WontFix Last 7 days Jan 04, 2010 issue 57 (fields needed) reported by st2002 - other field types needed like "BIGINT", "LONTTEXT" etc. other field types needed like "BIGINT", "LONTTEXT" etc. Jan 04, 2010 r76 (faster oz events) committed by ondrej.zara - faster oz events faster oz events Jan 03, 2010 issue 47 (No rubberband for selecting multiple tables) Status changed by ondrej.zara - Fixed in r75. Very nice work, thanks a lot! Status: Fixed Fixed in r75. Very nice work, thanks a lot! Status: Fixed Jan 03, 2010 r75 (#47 rubberband) committed by ondrej.zara - #47 rubberband #47 rubberband Jan 03, 2010 issue 55 (JavaScript errors triggered in IE) Status changed by ondrej.zara - Commited in r74. Status: Fixed Commited in r74. Status: Fixed Jan 03, 2010 r74 (#55) committed by ondrej.zara - #55 #55 Jan 03, 2010 issue 53 (Import with mysql 5.0.67) Status changed by ondrej.zara - Status: Invalid Status: Invalid Jan 03, 2010 issue 49 (Missing boolean/bit data type) Status changed by ondrej.zara - Fixed in r73, thanks! Status: Fixed Fixed in r73, thanks! Status: Fixed Jan 03, 2010 r73 (#49) committed by ondrej.zara - #49 #49 Jan 03, 2010 issue 54 (Always-active mouse move events are used for no good reason) Status changed by ondrej.zara - Commited in r72, thanks! Status: Fixed Commited in r72, thanks! Status: Fixed Jan 03, 2010 r72 (#54) committed by ondrej.zara - #54 #54 Jan 03, 2010 issue 56 (Minimap is not updated in IE) commented on by ondrej.zara - The VML code in wwwsqldesigner is old and developed primarily against IE6 and IE7. IE8's VML support is very tricky; some refactoring might be necessary. I will look into this soon. The VML code in wwwsqldesigner is old and developed primarily against IE6 and IE7. IE8's VML support is very tricky; some refactoring might be necessary. I will look into this soon. Last 30 days Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) commented on by kuba@mareimbrium.org - Heh, spoken too soon -- the other code that uses (for x in something) is in fact correct. All of the horkage smells like my own code. Apologies for the breakage, and patch is attached. Heh, spoken too soon -- the other code that uses (for x in something) is in fact correct. All of the horkage smells like my own code. Apologies for the breakage, and patch is attached. Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) commented on by kuba@mareimbrium.org - Heh, spoken too soon -- the other code that uses (for x in something) is in fact correct. All of the horkage smells like my own code. Apologies for the breakage, and patch is attached. Heh, spoken too soon -- the other code that uses (for x in something) is in fact correct. All of the horkage smells like my own code. Apologies for the breakage, and patch is attached. Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) commented on by kuba@mareimbrium.org - If so, then there are a few more problems like this in code that isn't mine ;) Updated patch on its way. If so, then there are a few more problems like this in code that isn't mine ;) Updated patch on its way. Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) commented on by ondrej.zara - Actually, IE's implementation is right here. Arrays should not be iterated with "for..in", because this lists all properties, which includes properties added to Array.prototype. This is a rather complex part of the JavaScript story; the only thing relevant to this issue is that arrays should be always iterated with a good-old for (var i=0;...) construct. Actually, IE's implementation is right here. Arrays should not be iterated with "for..in", because this lists all properties, which includes properties added to Array.prototype. This is a rather complex part of the JavaScript story; the only thing relevant to this issue is that arrays should be always iterated with a good-old for (var i=0;...) construct. Dec 28, 2009 issue 21 (export schema as picture) commented on by ondrej.zara - Keep in mind that this might be more difficult than you think. First, tables are HTML and there is no trivial html <-> svg bijection available. Second, there is no SVG in IE. Third, SVG lacks some features present in HTML+CSS, such as word/line wrapping - SVG test just does not wrap. Keep in mind that this might be more difficult than you think. First, tables are HTML and there is no trivial html <-> svg bijection available. Second, there is no SVG in IE. Third, SVG lacks some features present in HTML+CSS, such as word/line wrapping - SVG test just does not wrap. Dec 28, 2009 issue 21 (export schema as picture) commented on by kuba@mareimbrium.org - SVG could be generated by iterating over the tables, rows and connectors and presenting a pop-up window where it could be copied from. No code duplication is necessary, as all object properties (colors, sizes, etc) will be copied verbatim from existing DOM. I will work on it -- eventually. SVG could be generated by iterating over the tables, rows and connectors and presenting a pop-up window where it could be copied from. No code duplication is necessary, as all object properties (colors, sizes, etc) will be copied verbatim from existing DOM. I will work on it -- eventually. Dec 28, 2009 issue 56 (Minimap is not updated in IE) commented on by kuba@mareimbrium.org - Interestingly enough, if I change the browser mode to IE8 standards, the problem disappears. I have figured out how to get the canvas to work on IE8 without using IE7 mode, so that will be probably my line of attack. I have to set up IE6 and IE7 to test things out, too. Interestingly enough, if I change the browser mode to IE8 standards, the problem disappears. I have figured out how to get the canvas to work on IE8 without using IE7 mode, so that will be probably my line of attack. I have to set up IE6 and IE7 to test things out, too. Dec 28, 2009 issue 56 (Minimap is not updated in IE) commented on by kuba@mareimbrium.org - I'll try and figure out why it happens, if anyone has any hints -- they are obviously welcome! I'll try and figure out why it happens, if anyone has any hints -- they are obviously welcome! Dec 28, 2009 issue 56 (Minimap is not updated in IE) reported by kuba@mareimbrium.org - What steps will reproduce the problem? 1. Create/load tables. 2. Move tables around or select/deselect tables. What is the expected output? What do you see instead? Minimap doesn't update on selection/dragging of tables. What version of the product are you using? On what operating system? svn rev 71 + fixes for issue 55 , IE8 on XP SP3 What steps will reproduce the problem? 1. Create/load tables. 2. Move tables around or select/deselect tables. What is the expected output? What do you see instead? Minimap doesn't update on selection/dragging of tables. What version of the product are you using? On what operating system? svn rev 71 + fixes for issue 55 , IE8 on XP SP3 Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) commented on by kuba@mareimbrium.org - Obviously I'm responsible for this breakage ;). I've only now gotten to testing in IE. Obviously I'm responsible for this breakage ;). I've only now gotten to testing in IE. Dec 28, 2009 issue 55 (JavaScript errors triggered in IE) reported by kuba@mareimbrium.org - What steps will reproduce the problem? 1. Try to use wwwsqldesigner in IE8. 2. JavaScript runtime errors show up in debug console What version of the product are you using? On what operating system? svn rev 71 Please provide any additional information below. Patch attached. IE has a JS bug in its implementation of arrays, for (x in array) will iterate methods in absence of array elements. What steps will reproduce the problem? 1. Try to use wwwsqldesigner in IE8. 2. JavaScript runtime errors show up in debug console What version of the product are you using? On what operating system? svn rev 71 Please provide any additional information below. Patch attached. IE has a JS bug in its implementation of arrays, for (x in array) will iterate methods in absence of array elements. Dec 28, 2009 issue 54 (Always-active mouse move events are used for no good reason) reported by kuba@mareimbrium.org - What steps will reproduce the problem? Move the mouse - SQL.Table.move and SQL.Map.move fire while moving the mouse around even though there are no tables, and nothing is being dragged (neither a table nor a map item). This may be a contributor to dnd sluggishness in Opera. What is the expected output? What do you see instead? SQL.Table.move should be invoked only when dragging a table. SQL.Map.move should be invoked only when dragging a map item. What version of the product are you using? On what operating system? svn rev 71 Please provide any additional information below. Patch is attached. What steps will reproduce the problem? Move the mouse - SQL.Table.move and SQL.Map.move fire while moving the mouse around even though there are no tables, and nothing is being dragged (neither a table nor a map item). This may be a contributor to dnd sluggishness in Opera. What is the expected output? What do you see instead? SQL.Table.move should be invoked only when dragging a table. SQL.Map.move should be invoked only when dragging a map item. What version of the product are you using? On what operating system? svn rev 71 Please provide any additional information below. Patch is attached. Dec 27, 2009 issue 45 (Support using plain delete (backspace) key to delete rows/ta...) commented on by atrophic - I also had an issue where I lost changes because I clicked backspace when I thought I was editing text. It caused me to save after every change from then on, which is not very productive. Alt - left arrow still works as back, as does the back button. I agree that using your browser for this sort of task changes the expected behavior of the browser. However, misclicking a text field you plan to change the name of and instead losing all your work is a worse user experience than losing the navigation abilities of the back button. I also had an issue where I lost changes because I clicked backspace when I thought I was editing text. It caused me to save after every change from then on, which is not very productive. Alt - left arrow still works as back, as does the back button. I agree that using your browser for this sort of task changes the expected behavior of the browser. However, misclicking a text field you plan to change the name of and instead losing all your work is a worse user experience than losing the navigation abilities of the back button. Dec 27, 2009 issue 49 (Missing boolean/bit data type) commented on by atrophic - Part of this bug was me not reading directions. I had changed the database I was designing against after I started the design, which did not work (as designed). However, after starting from scratch, MySQL was still missing the BIT data type, which was an alias for tinyint(1) prior to version 5.0.3, but is now an official data type (albeit with some confusing implementation). I added it to the Miscellaneous section, where it is found in most other database engines' datatypes.xml. Attached is my attempt at a patch. kuba, thanks for reminding me about this ;) Part of this bug was me not reading directions. I had changed the database I was designing against after I started the design, which did not work (as designed). However, after starting from scratch, MySQL was still missing the BIT data type, which was an alias for tinyint(1) prior to version 5.0.3, but is now an official data type (albeit with some confusing implementation). I added it to the Miscellaneous section, where it is found in most other database engines' datatypes.xml. Attached is my attempt at a patch. kuba, thanks for reminding me about this ;) Dec 26, 2009 issue 49 (Missing boolean/bit data type) commented on by kuba@mareimbrium.org - atrophic: feel free to let me know what database it is, and I can make a patch if you can't. atrophic: feel free to let me know what database it is, and I can make a patch if you can't. Dec 26, 2009 issue 29 (Drag n Drop (foreign keys, re-order fields)) commented on by k...@mareimbrium.org - Started working on it ;) Started working on it ;) Dec 26, 2009 issue 47 (No rubberband for selecting multiple tables) commented on by k...@mareimbrium.org - Implemented in the attached patch. Implemented in the attached patch. Dec 20, 2009 issue 53 (Import with mysql 5.0.67) commented on by benoit.20cent - I agree with you, the catalog database itself is a database containing the metadata but i am a problem, after several test I can pass the query if i'was logged on the basis INFORMATION_SCHEMA. setup_import function () ( define ( "SERVER", "localhost"); define ( "USER", "root"); define ( "PASSWORD", "xxxxxx"); define ( "DB", "INFORMATION_SCHEMA"); ) In the $ _GET, I pass the name of my database ... and it's work Best regards I agree with you, the catalog database itself is a database containing the metadata but i am a problem, after several test I can pass the query if i'was logged on the basis INFORMATION_SCHEMA. setup_import function () ( define ( "SERVER", "localhost"); define ( "USER", "root"); define ( "PASSWORD", "xxxxxx"); define ( "DB", "INFORMATION_SCHEMA"); ) In the $ _GET, I pass the name of my database ... and it's work Best regards Dec 20, 2009 issue 53 (Import with mysql 5.0.67) commented on by ondrej.zara - I cannot agree here. MySQL 5 uses the information_schema to store table/column metadata, one can easily verify that. On my linux box with MySQL 5.0.51, I can do: mysql> use information_schema; mysql> describe tables; mysql> describe columns; Both "describe" statements show that there truly are TABLES and COLUMNS tables. Therefore, I believe that your issue is caused by something else. I cannot agree here. MySQL 5 uses the information_schema to store table/column metadata, one can easily verify that. On my linux box with MySQL 5.0.51, I can do: mysql> use information_schema; mysql> describe tables; mysql> describe columns; Both "describe" statements show that there truly are TABLES and COLUMNS tables. Therefore, I believe that your issue is caused by something else. Dec 20, 2009 issue 53 (Import with mysql 5.0.67) reported by benoit.20cent - What steps will reproduce the problem? 1. Import bdd with mysql 5.0.67 2. You sea an error php that explain a problem in query SELECT * FROM TABLES WHERE TABLE_SCHEMA = '".$db."'" What is the expected output? What do you see instead? You sea an error php that explain a problem in query SELECT * FROM TABLES WHERE TABLE_SCHEMA = '".$db."'" in a reponse What version of the product are you using? On what operating system? I'm using mysql 5.0.67 in local environement on linux Please provide any additional information below. In mysql 5 the query SELECT * FROM TABLES WHERE TABLE_SCHEMA = 'XXX' was replace by SHOW TABLES FROM 'XXX'. The same problème occur with this query SELECT * FROM COLUMNS WHERE TABLE_NAME, she was replace by SHOW COLUMNS FROM 'TABLE' FROM 'DB'; What steps will reproduce the problem? 1. Import bdd with mysql 5.0.67 2. You sea an error php that explain a problem in query SELECT * FROM TABLES WHERE TABLE_SCHEMA = '".$db."'" What is the expected output? What do you see instead? You sea an error php that explain a problem in query SELECT * FROM TABLES WHERE TABLE_SCHEMA = '".$db."'" in a reponse What version of the product are you using? On what operating system? I'm using mysql 5.0.67 in local environement on linux Please provide any additional information below. In mysql 5 the query SELECT * FROM TABLES WHERE TABLE_SCHEMA = 'XXX' was replace by SHOW TABLES FROM 'XXX'. The same problème occur with this query SELECT * FROM COLUMNS WHERE TABLE_NAME, she was replace by SHOW COLUMNS FROM 'TABLE' FROM 'DB'; Dec 20, 2009 r71 (japanese locale, thanks to Kado Masanori) committed by ondrej.zara - japanese locale, thanks to Kado Masanori japanese locale, thanks to Kado Masanori Dec 16, 2009 r70 (italian translation, thanks to Paolo Lulli) committed by ondrej.zara - italian translation, thanks to Paolo Lulli italian translation, thanks to Paolo Lulli Dec 15, 2009 r69 (removeevent fix) committed by ondrej.zara - removeevent fix removeevent fix Dec 14, 2009 r68 (new oz.js) committed by ondrej.zara - new oz.js new oz.js Dec 14, 2009 r67 (new oz.js) committed by ondrej.zara - new oz.js new oz.js Dec 07, 2009 r66 (fixes for vfp9 db definition) committed by ondrej.zara - fixes for vfp9 db definition fixes for vfp9 db definition Older Dec 03, 2009 r65 (Visual FoxPro datatype definition, thanks to Mirek Zvolsky) committed by ondrej.zara - Visual FoxPro datatype definition, thanks to Mirek Zvolsky Visual FoxPro datatype definition, thanks to Mirek Zvolsky Dec 02, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by ondrej.zara - The missing "=" is just some fixed stuff present in latest SVN revisions. JS unfortunately needs all XML files server with text/xml or application/xml, so your workaround is certainly the best you can do, given these circumstances. Congratulations :) The missing "=" is just some fixed stuff present in latest SVN revisions. JS unfortunately needs all XML files server with text/xml or application/xml, so your workaround is certainly the best you can do, given these circumstances. Congratulations :) Dec 02, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - Problem solved. :) After reading [http://www.se.eecs.uni-kassel.de/~thm/Linux/mozilla-xml-xsl.html] and [http://www.ibm.com/developerworks/xml/library/x-tipapachexhtml/index.html] I wrote a small .htaccess file and placed it in the "db/mysql" directory. {{{ RewriteEngine on RewriteCond %{REQUEST_URI} \.xsl$ RewriteRule .* - [T=application/xml] }}} Now the SQL generation works. Not sure if this is the best way to solve this problem but is a functioning workaround. Problem solved. :) After reading [http://www.se.eecs.uni-kassel.de/~thm/Linux/mozilla-xml-xsl.html] and [http://www.ibm.com/developerworks/xml/library/x-tipapachexhtml/index.html] I wrote a small .htaccess file and placed it in the "db/mysql" directory. {{{ RewriteEngine on RewriteCond %{REQUEST_URI} \.xsl$ RewriteRule .* - [T=application/xml] }}} Now the SQL generation works. Not sure if this is the best way to solve this problem but is a functioning workaround. Dec 02, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - The missing '=' character is no longer a problem. This was caused by my browser using presumably an older cached version of the file. Now the only difference seems to be the content type. The missing '=' character is no longer a problem. This was caused by my browser using presumably an older cached version of the file. Now the only difference seems to be the content type. Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - I've also just compared the headers I get from the demo with the headers I get from my server and discovered that the response header content type differs. The length of the response differs also by one byte but this is likely due to a new line at the end of the file. From Demo: Content-Type application/xml From my server: Content-Type text/x-xslt Any idea what's going on here ? I've also just compared the headers I get from the demo with the headers I get from my server and discovered that the response header content type differs. The length of the response differs also by one byte but this is likely due to a new line at the end of the file. From Demo: Content-Type application/xml From my server: Content-Type text/x-xslt Any idea what's going on here ? Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - I've test a couple variations and determined that the XSL that my browser recieves has one difference. On line 96 {{{ <xsl:text> COMMENT='</xsl:text> }}} the '=' character is missing. The file "db/mysql/output.xsl" on my local server contains the '=' character. When I compare the response from the demo application with my local server copy of "db/mysql/output.xsl" they are identical and the SQL generation works. Only when I get the response from my local server is the '=' character missing in the response. I thought it may have something to do with PHP short tags which I have activated but I changed this and the error still occurs. This is a strange problem. Here are the request and response headers for the request as seen in firebug Response Headers Date Tue, 01 Dec 2009 08:09:02 GMT Server Apache/2.2.10 (Linux/SUSE) Last-Modified Thu, 05 Nov 2009 08:03:54 GMT Etag "64371-df8-4779b2b200e80" Accept-Ranges bytes Content-Length 3576 Content-Type text/x-xslt Request Headers Host ahp3 User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-2.1 Firefox/3.5 Accept text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://ahp3/sqldesigner/ Cookie fe_typo_user=41bfbb95d9 I've test a couple variations and determined that the XSL that my browser recieves has one difference. On line 96 {{{ <xsl:text> COMMENT='</xsl:text> }}} the '=' character is missing. The file "db/mysql/output.xsl" on my local server contains the '=' character. When I compare the response from the demo application with my local server copy of "db/mysql/output.xsl" they are identical and the SQL generation works. Only when I get the response from my local server is the '=' character missing in the response. I thought it may have something to do with PHP short tags which I have activated but I changed this and the error still occurs. This is a strange problem. Here are the request and response headers for the request as seen in firebug Response Headers Date Tue, 01 Dec 2009 08:09:02 GMT Server Apache/2.2.10 (Linux/SUSE) Last-Modified Thu, 05 Nov 2009 08:03:54 GMT Etag "64371-df8-4779b2b200e80" Accept-Ranges bytes Content-Length 3576 Content-Type text/x-xslt Request Headers Host ahp3 User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-2.1 Firefox/3.5 Accept text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://ahp3/sqldesigner/ Cookie fe_typo_user=41bfbb95d9 Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by ondrej.zara - Ok, please use Firebug to see if the .xsl template necessary for SQL statement creation is fetched properly. The requested file should be "db/mysql/output.xsl". Ok, please use Firebug to see if the .xsl template necessary for SQL statement creation is fetched properly. The requested file should be "db/mysql/output.xsl". Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - The problem occurred in the latest version 2.4. I've also checked out the most recent SVN read-only version and the problem still occurs. The problem occurred in the latest version 2.4. I've also checked out the most recent SVN read-only version and the problem still occurs. Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - Thanks for the quick response. The options is set to mysql. The problem does NOT occur with the sample database. In that case I get the SQL output. Not sure if this plays a role, but i've tried to set all my collations to be unicode. UTF-8 charset and utf-unicode-ci for the tables and fields. Thanks for the quick response. The options is set to mysql. The problem does NOT occur with the sample database. In that case I get the SQL output. Not sure if this plays a role, but i've tried to set all my collations to be unicode. UTF-8 charset and utf-unicode-ci for the tables and fields. Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by ondrej.zara - Hi, please tell us what DB datatypes do you use (Options -> Database for new designs). Also, does the problem happen on the sample database view, the http://ondras.zarovi.cz/sql/demo/?keyword=default ? Hi, please tell us what DB datatypes do you use (Options -> Database for new designs). Also, does the problem happen on the sample database view, the http://ondras.zarovi.cz/sql/demo/?keyword=default ? Dec 01, 2009 Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - Excellent tool, thank you very much!!! I still have one problem. Import/load/save from DB are working fine. XML Save is also working. The problem is in generating SQL code for the table definitions. I get the error XML error: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIXSLTProcessor.importStylesheet] Not really sure where to begin with this one. Am I missing something or is it possible to use the XML definitions to create the tables in the DB ? I'm using firefox 3.5, MySql 5.0.67 and Suse 11.1 Thanks for any help Excellent tool, thank you very much!!! I still have one problem. Import/load/save from DB are working fine. XML Save is also working. The problem is in generating SQL code for the table definitions. I get the error XML error: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIXSLTProcessor.importStylesheet] Not really sure where to begin with this one. Am I missing something or is it possible to use the XML definitions to create the tables in the DB ? I'm using firefox 3.5, MySql 5.0.67 and Suse 11.1 Thanks for any help

Manual (WWW SQL Designer user manual) Wiki page commented on by mym...@andypotter.org - I've test a couple variations and determined that the XSL that my browser recieves has one difference. On line 96 {{{ <xsl:text> COMMENT='</xsl:text> }}} the '=' character is missing. The file "db/mysql/output.xsl" on my local server contains the '=' character. When I compare the response from the demo application with my local server copy of "db/mysql/output.xsl" they are identical and the SQL generation works. Only when I get the response from my local server is the '=' character missing in the response. I thought it may have something to do with PHP short tags which I have activated but I changed this and the error still occurs. This is a strange problem. Here are the request and response headers for the request as seen in firebug Response Headers Date Tue, 01 Dec 2009 08:09:02 GMT Server Apache/2.2.10 (Linux/SUSE) Last-Modified Thu, 05 Nov 2009 08:03:54 GMT Etag "64371-df8-4779b2b200e80" Accept-Ranges bytes Content-Length 3576 Content-Type text/x-xslt Request Headers Host ahp3 User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-2.1 Firefox/3.5 Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://ahp3/sqldesigner/ Cookie fe_typo_user=41bfbb95d9

I've test a couple variations and determined that the XSL that my browser recieves has one difference. On line 96 {{{ <xsl:text> COMMENT='</xsl:text> }}} the '=' character is missing. The file "db/mysql/output.xsl" on my local server contains the '=' character. When I compare the response from the demo application with my local server copy of "db/mysql/output.xsl" they are identical and the SQL generation works. Only when I get the response from my local server is the '=' character missing in the response. I thought it may have something to do with PHP short tags which I have activated but I changed this and the error still occurs. This is a strange problem. Here are the request and response headers for the request as seen in firebug Response Headers Date Tue, 01 Dec 2009 08:09:02 GMT Server Apache/2.2.10 (Linux/SUSE) Last-Modified Thu, 05 Nov 2009 08:03:54 GMT Etag "64371-df8-4779b2b200e80" Accept-Ranges bytes Content-Length 3576 Content-Type text/x-xslt Request Headers Host ahp3 User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-2.1 Firefox/3.5 Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://ahp3/sqldesigner/ Cookie fe_typo_user=41bfbb95d9

Yesterday

Last 7 days

Last 30 days

Older