search

tberthel / jiql

Automatically exported from code.google.com/p/jiql
0 stars 0 forks source link

Insert Errors #3

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When inserting data that contains some complex text JIQL parsing fails.

Example:

INSERT INTO transforminfo VALUES ('TestStore Insert 
CUSTOMIZER_TRANSFORM_INFO_NAME','TestStore','views.business.context.modules.stor
efront.customizer.template.InsertCustomizerValidationView','','template/
genericRootTemplateObjectConfig.xml','<?xml version="1.0" encoding="UTF-8" 
standalone="no"?><!--
Copyright (c) 2002=2004 All Binary.
--><OBJECTCONFIG_NAME 
OBJECTCONFIG_NAME="GenericRootTransformInfoObjectConfig">

   <TRANSFORM_COMPONENTS_NAME>

      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
ROOT_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>
      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
GENERATOR_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>
      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
TRANSFORM_COMPONENTS_PREVIEW ROOT_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>
      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
TRANSFORM_COMPONENTS_PREVIEW GENERATOR_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>
      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
TRANSFORM_COMPONENTS_SMALL_PREVIEW ROOT_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>
      <COMPONENT_NAME TRANSFORM_INFO_NAME="$STOREFRONT_NAME 
TRANSFORM_COMPONENTS_SMALL_PREVIEW GENERATOR_TRANSFORM_INFO_NAME">
      </COMPONENT_NAME>

   </TRANSFORM_COMPONENTS_NAME>

</OBJECTCONFIG_NAME>','','','','','1269841940425','1269841940425')

I have found to issues:

1.  What I have found is that the end is missing for some inserts. That is 
the last single quote  and closing parens ') are gone from the end.

2.  jiql_replace_comma is not removed after the XML data column in the 
insert statement.

Note you could increase performance considerably by not doing so much 
string concatenation.

Original issue reported on code.google.com by travisbe...@gmail.com on 29 Mar 2010 at 7:02

GoogleCodeExporter commented 9 years ago 
Turns out that if I encode my XML that the insertion problems go away.

So it's entirely how individual column values are parsed.  I have had this 
problem 
with some database implementations long ago.  As such I will just encode the 
XML until 
a fix is in.

Original comment by travisbe...@gmail.com on 29 Mar 2010 at 1:25

GoogleCodeExporter commented 9 years ago 
I am using jiql from last 4 months on GAE. Now i am going to leave it and use 
JDO. there are serious performance issues with jiql. as soon as the data grown 
in the application, jiql response becomes uncertain. so many times it gave 
improper result or breaks. it not even work properly for a table with 3000 
records.

Original comment by walida...@gmail.com on 2 Dec 2010 at 12:21