Hi Ryan,
class names can't start with numbers so far. We could fix it, but to let
you go on can you prefix all your classes with a character, like:

c240a49d0-2596-4789-8487-d8c6afdfd8d1

Lvc@



On 27 June 2014 19:09, Ryan Conrad <[email protected]> wrote:

> Scratch that....I thoguht my rebuild wiped my old libs but it just
> appended the new ones on and kept old ones as well.
>
> Still didnt fix the problem:
> ODocument system = db.newInstance(systemUuid); -> BREAKS
>
> java.lang.NumberFormatException: For input string:
> "240a49d0-2596-4789-8487-d8c6afdfd8d1"
>         at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>         at java.lang.Integer.parseInt(Integer.java:492)
>         at java.lang.Integer.parseInt(Integer.java:527)
>         at
> com.orientechnologies.orient.client.remote.OStorageRemote.getClusterIdByName(OStorageRemote.java:1146)
>         at
> com.orientechnologies.orient.client.remote.OStorageRemoteThread.getClusterIdByName(OStorageRemoteThread.java:473)
>         at
> com.orientechnologies.orient.core.db.raw.ODatabaseRaw.getClusterIdByName(ODatabaseRaw.java:384)
>         at
> com.orientechnologies.orient.core.db.ODatabaseWrapperAbstract.getClusterIdByName(ODatabaseWrapperAbstract.java:186)
>         at
> com.orientechnologies.orient.core.metadata.schema.OSchemaShared.createClass(OSchemaShared.java:136)
>         at
> com.orientechnologies.orient.core.metadata.schema.OSchemaShared.createClass(OSchemaShared.java:129)
>         at
> com.orientechnologies.orient.core.metadata.schema.OSchemaShared.getOrCreateClass(OSchemaShared.java:161)
>         at
> com.orientechnologies.orient.core.metadata.schema.OSchemaShared.getOrCreateClass(OSchemaShared.java:153)
>         at
> com.orientechnologies.orient.core.metadata.schema.OSchemaProxy.getOrCreateClass(OSchemaProxy.java:67)
>         at
> com.orientechnologies.orient.core.record.ORecordSchemaAwareAbstract.setClassName(ORecordSchemaAwareAbstract.java:395)
>         at
> com.orientechnologies.orient.core.record.impl.ODocument.<init>(ODocument.java:217)
>         at
> com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.newInstance(ODatabaseDocumentTx.java:190)
>
>
> On Friday, June 27, 2014 12:59:14 PM UTC-4, Ryan Conrad wrote:
>>
>> I changed over all my .jars and server-config but it still says this:
>>
>> INFO OrientDB Server v1.7-rc2 is active
>>
>> on startup.  Is this still what it shows when running 1.7.4?  If so then
>> it doesnt work to fix the numberformatexception
>>
>> On Friday, June 27, 2014 12:13:23 PM UTC-4, Lvc@ wrote:
>>>
>>> Hi,
>>> We fixed this in 1.7.4. Can you try this version?
>>>
>>> Lvc@
>>>
>>>
>>> On 27 June 2014 18:07, Ryan Conrad <[email protected]> wrote:
>>>
>>>> Same problem here:
>>>>
>>>> NumberFormatException For input string: 
>>>> "42ad4ad3-39f1-4b99-8f39-68bad2030020"
>>>> on a newInstance call cause this will be my class name. (table name)
>>>>
>>>> Did anyone find a solution to this?
>>>>
>>>>
>>>> On Wednesday, April 2, 2014 8:56:25 AM UTC-4, MrFT wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> When checking if an edge already exists before creating a new one (for
>>>>> an import)
>>>>> I was doing:
>>>>>
>>>>> select in.key, out.key
>>>>> from has_property
>>>>> where out.key = 'a2adb112-a3a4-11e3-ace8-005056872b95' and in.key =
>>>>> 'a3eb10b0-a3a4-11e3-ace8-005056872b95'
>>>>>
>>>>> This works, but it is slow, since you're not using the index to lookup
>>>>> the edges.
>>>>>
>>>>> So I rewrote it like this (as I did for a few other similar queries):
>>>>>
>>>>> select key
>>>>> from School
>>>>> where key = 'a2adb112-a3a4-11e3-ace8-005056872b95'
>>>>>       and in( 'has_property' )[ key = 
>>>>> 'a3eb10b0-a3a4-11e3-ace8-005056872b95'
>>>>> ].key is not null
>>>>>
>>>>>  This will start by using the index to find the school with key=xxx,
>>>>> and then look through the edges to find if it is connected to another node
>>>>> with key yyy.
>>>>>
>>>>> Unfortunately, in this case it didn't work, and i get:
>>>>> java.lang.NumberFormatException: For input string: " key = 'a3eb10b0"
>>>>>
>>>>> (There is a string index on that 'key' property)
>>>>>
>>>>> Similar queries were working without problems, for example:
>>>>> select key
>>>>> from School
>>>>> where key = 'a2a691e8-a3a4-11e3-ace8-005056872b95' and in(
>>>>> 'provides_services_for' )[ institutionNumber= '114546' ].institutionNumber
>>>>> is not null
>>>>>
>>>>> is working as expected.
>>>>>
>>>>> Any ideas what might be wrong?
>>>>>
>>>>> I am using the 1.7 snapshot version from a few days ago (1st of april
>>>>> I think)...
>>>>>
>>>>   --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "OrientDB" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to