No worries, glad you got it sorted.

Mark

On Thu, Mar 5, 2009 at 10:21 AM, Chris Woerz <[email protected]> wrote:
>
> I think i have it licked, not sure when this changed but we recently
> upgraded from ~0.6 to 1.1 and maybe the default for numeric fields
> changed? anyway turns out that i didnt notice that LUFACILITYSTATUS_FK
> was getting autopopulated with 0 when it in the past was getting ""
> which breaks the relationship with its table. thank you for your help
> and sorry for that.
>
> transfer is a really great tool that i enjoy working with and reading
> your posts i hope to know more about it then i do someday :)
>
> On Mar 2, 5:14 pm, Mark Mandel <[email protected]> wrote:
>> What happens if you try and do an insert without transfer, with a
>> normal <cfquery> and <cfqueryparam> does it work that way?
>>
>> Just trying to narrow down the issue.
>>
>> May be worth attempting to set the PK as a string?
>>
>> Mark
>>
>>
>>
>> On Tue, Mar 3, 2009 at 11:09 AM, Chris Woerz <[email protected]> wrote:
>>
>> > this error is when i am inserting.
>> > this is my code minus the other columns
>>
>> >        facilityformbean = getModelGlue().getBean("facilityformbean");
>> >        facilityformbean.setFacility_PK( url.facility_pk ); <!--
>> > url.facility_pk = 20090226114107-->
>> >        id = getModelGlue().getBean("facility").save ( facilityformbean );
>>
>> > and this is the query transfer generates
>>
>> >        INSERT INTO     facility
>> > (FACILITYID,RECEIPTDATE,INSURANCECOMMENTS,DATECERTIFIED,ONINDIANLANDS,PHONE,LUFACILITYSTATUS_FK,OTHERINFO,TIMESTAMP,COMMENTS,USERNAME,LUFACILITYTYPE_FK,REGIONALOFFICE_FK,LUOWNERTYPE_FK,NEAR_DW_SOURCE,FACILITY_PK)
>> >        VALUES ( (param 1) , (param 2) , (param 3) , (param 4) , (param 5) ,
>> > (param 6) , (param 7) , (param 8) , (param 9) , (param 10) , (param
>> > 11) , (param 12) , (param 13) , (param 14) , (param 15) , (param
>> > 16) )
>>
>> >        (param 1) = [type='IN', class='java.lang.String', value='',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 2) = [type='IN', class='java.sql.Timestamp', 
>> > value='2009-02-27
>> > 13:10:08.153', sqltype='cf_sql_timestamp'] ,
>> >        (param 3) = [type='IN', class='java.lang.String', value='',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 4) = [type='IN', class='java.sql.Timestamp', 
>> > value='2009-02-27
>> > 13:10:08.153', sqltype='cf_sql_timestamp'] ,
>> >        (param 5) = [type='IN', class='java.lang.Double', value='0.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 6) = [type='IN', class='java.lang.String', value='',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 7) = [type='IN', class='java.lang.Double', value='0.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 8) = [type='IN', class='java.lang.String', value='',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 9) = [type='IN', class='java.sql.Timestamp', 
>> > value='2009-02-27
>> > 13:10:08.153', sqltype='cf_sql_timestamp'] ,
>> >        (param 10) = [type='IN', class='java.lang.String', value='UST',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 11) = [type='IN', class='java.lang.String', value='',
>> > sqltype='cf_sql_varchar'] ,
>> >        (param 12) = [type='IN', class='java.lang.Double', value='1.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 13) = [type='IN', class='java.lang.Double', value='0.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 14) = [type='IN', class='java.lang.Double', value='1.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 15) = [type='IN', class='java.lang.Double', value='1.0',
>> > sqltype='cf_sql_float'] ,
>> >        (param 16) = [type='IN', class='java.lang.Double',
>> > value='2.0090226114107E13', sqltype='cf_sql_float']
>>
>> > the whole tranfer.xml section for this table is...
>>
>> >        <object name="facility" table="facility">
>> >                <id name="FACILITY_PK" type="numeric" generate="true" />
>> >                <property name="FACILITYID" type="string" 
>> > column="FACILITYID" />
>> >                <property name="RECEIPTDATE" type="date" 
>> > column="RECEIPTDATE"
>> > nullable="true"/>
>> >                <property name="INSURANCECOMMENTS" type="string"
>> > column="INSURANCECOMMENTS" />
>> >                <property name="DATECERTIFIED" type="date" 
>> > column="DATECERTIFIED"
>> > nullable="true" />
>> >                <property name="ONINDIANLANDS" type="numeric"
>> > column="ONINDIANLANDS" />
>> >                <property name="PHONE" type="string" column="PHONE" />
>> >                <property name="LUFACILITYSTATUS_FK" type="numeric"
>> > column="LUFACILITYSTATUS_FK" />
>> >                <property name="OTHERINFO" type="string" column="OTHERINFO" 
>> > />
>> >                <property name="TIMESTAMP" type="date" column="TIMESTAMP" />
>> >                <property name="COMMENTS" type="string" column="COMMENTS" />
>> >                <property name="USERNAME" type="string" column="USERNAME" />
>> >                <property name="LUFACILITYTYPE_FK" type="numeric"
>> > column="LUFACILITYTYPE_FK" />
>> >                <property name="REGIONALOFFICE_FK" type="numeric"
>> > column="REGIONALOFFICE_FK" />
>> >                <property name="LUOWNERTYPE_FK" type="numeric"
>> > column="LUOWNERTYPE_FK" />
>> >                <property name="NEAR_DW_SOURCE" type="numeric"
>> > column="NEAR_DW_SOURCE" nullable="true" />
>> >        </object>
>>
>> > sorry for the non transfer parts of the syntax, i havent ever used
>> > transfer without modelglue/coldspring.
>>
>> > On Mar 2, 4:37 pm, Mark Mandel <[email protected]> wrote:
>> >> Is it a case of it coming out of the database in Scientific notation,
>> >> b/c it is so large?
>>
>> >> How does it work usually with normal CFML Queries and Query Params?
>>
>> >> Mark
>>
>> >> On Tue, Mar 3, 2009 at 10:36 AM, Chris Woerz <[email protected]> wrote:
>>
>> >> > I completely agree with you about the nightmare that this will be :P
>>
>> >> > the data_type in the database(oracle) is NUMBER(22,0)
>> >> > and in the transfer def is <id name="id" type="numeric" column="id"
>> >> > generate="true"/>
>>
>> >> > most of the time it works fine, but every once in a while it gets
>> >> > converted to scientific notation. which is fine if it happens in a
>> >> > <form> because i can javacast() it on the page but for transfer there
>> >> > is no workaround that i could find.
>>
>> >> > as much as i would love to slash and burn we have 30 years of historic
>> >> > data in there so not much i can do about the keys.
>>
>> >> > On Mar 2, 3:54 pm, Brian Kotek <[email protected]> wrote:
>> >> >> Is this a string field or a numeric field? It sounds like the type 
>> >> >> defined
>> >> >> in the Transfer config is not the correct type?
>>
>> >> >> Aside from that, I'm having a hard time understanding why anyone would 
>> >> >> use a
>> >> >> value like this as a primary key. If two records are created at the 
>> >> >> same
>> >> >> time, what happens? One just throws an error? If you have control of 
>> >> >> the
>> >> >> schema, can you change it to an autoincrementing id or at least a 
>> >> >> UUID? This
>> >> >> sounds like it's going to turn into a nightmare later.
>>
>> >> >> On Mon, Mar 2, 2009 at 5:20 PM, Chris Woerz <[email protected]> 
>> >> >> wrote:
>>
>> >> >> > I have a table with a primary key that based on the datetime at 
>> >> >> > record
>> >> >> > creation (ie 20090226114107) recently when i invoke save() i get an
>> >> >> > error because the primary key that transfer tries to insert is
>> >> >> > '2.0090226114107E13'. is there anyway to resolve this? im pretty new
>> >> >> > to transfer and i inherited an app that im not sure was setup
>> >> >> > correctly.
>>
>> >> --
>> >> E: [email protected]
>> >> W:www.compoundtheory.com
>>
>> --
>> E: [email protected]
>> W:www.compoundtheory.com
> >
>



-- 
E: [email protected]
W: www.compoundtheory.com

--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer

You received this message because you are subscribed to the Google Groups 
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to