Riduidel/gaedo issues and pull requests

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#48 - Trying to load a vertex of a subclass of current class miserably fails

Issue - State: closed - Opened by Riduidel almost 12 years ago - 1 comment
Labels: bug

#47 - Under some circumstances, field path is not correctly computed

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#47 - Under some circumstances, field path is not correctly computed

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#47 - Under some circumstances, field path is not correctly computed

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#47 - Under some circumstances, field path is not correctly computed

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#47 - Under some circumstances, field path is not correctly computed

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#46 - Searching a non-existing item may create it.

Issue - State: closed - Opened by Riduidel almost 12 years ago - 3 comments
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#45 - CollectionLazyLoader doesn't use focused graph for loading vertices

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#44 - Searching edge in named graphs

Issue - State: closed - Opened by xmethos almost 12 years ago - 2 comments

#43 - AbstractTupeTransformer#getVertexFor doesn't honor the given cascade

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#43 - AbstractTupeTransformer#getVertexFor doesn't honor the given cascade

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#43 - AbstractTupeTransformer#getVertexFor doesn't honor the given cascade

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#43 - AbstractTupeTransformer#getVertexFor doesn't honor the given cascade

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#43 - AbstractTupeTransformer#getVertexFor doesn't honor the given cascade

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#42 - Bugfix for #41 introduced a regression !

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#42 - Bugfix for #41 introduced a regression !

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#42 - Bugfix for #41 introduced a regression !

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#41 - PERSIST cascade should not imply to update property

Issue - State: closed - Opened by alexblanquart almost 12 years ago
Labels: question

#40 - bugfix

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#40 - bugfix

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#40 - bugfix

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#40 - bugfix

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#39 - Let's try this again

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#39 - Let's try this again

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#39 - Let's try this again

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#39 - Let's try this again

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#38 - Fixed that for you

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 3 comments

#38 - Fixed that for you

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 3 comments

#38 - Fixed that for you

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 3 comments

#38 - Fixed that for you

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 3 comments

#38 - Fixed that for you

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 3 comments

#37 - Pull modifications enforcing order on collections

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#36 - informer-generator fix, compilation error

Pull Request - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#35 - It is possible to fail loading some vertices

Issue - State: open - Opened by Riduidel almost 12 years ago
Labels: bug

#34 - The order of ordered Collections is not conserved

Issue - State: closed - Opened by Kricket almost 12 years ago - 1 comment

#33 - Deleting a null item triggers a NullPointerException

Issue - State: closed - Opened by Riduidel almost 12 years ago

#33 - Deleting a null item triggers a NullPointerException

Issue - State: closed - Opened by Riduidel almost 12 years ago

#32 - Current implementation of cascade allows fields to be replaced by null values event when their cascade prevents it

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#32 - Current implementation of cascade allows fields to be replaced by null values event when their cascade prevents it

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#32 - Current implementation of cascade allows fields to be replaced by null values event when their cascade prevents it

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#32 - Current implementation of cascade allows fields to be replaced by null values event when their cascade prevents it

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#31 - Linking to an untyped uri vertex prevents loading

Issue - State: closed - Opened by Riduidel almost 12 years ago - 2 comments
Labels: bug

#31 - Linking to an untyped uri vertex prevents loading

Issue - State: closed - Opened by Riduidel almost 12 years ago - 2 comments
Labels: bug

#31 - Linking to an untyped uri vertex prevents loading

Issue - State: closed - Opened by Riduidel almost 12 years ago - 2 comments
Labels: bug

#31 - Linking to an untyped uri vertex prevents loading

Issue - State: closed - Opened by Riduidel almost 12 years ago - 2 comments
Labels: bug

#31 - Linking to an untyped uri vertex prevents loading

Issue - State: closed - Opened by Riduidel almost 12 years ago - 2 comments
Labels: bug

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#30 - Add handling of URI in TypeUtils

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: enhancement

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#29 - Cascading set on properties not taken into account when updating them

Issue - State: closed - Opened by alexblanquart almost 12 years ago

#28 - GraphBasedPropertyBuilder doesn't use the TypeUtils resolution mechanism

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#28 - GraphBasedPropertyBuilder doesn't use the TypeUtils resolution mechanism

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#28 - GraphBasedPropertyBuilder doesn't use the TypeUtils resolution mechanism

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#28 - GraphBasedPropertyBuilder doesn't use the TypeUtils resolution mechanism

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#27 - Using focusOn on GraphBasedMappingService may result in non-focused service be also focused

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#26 - Updating an enum can create UnableToSetException

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#26 - Updating an enum can create UnableToSetException

Issue - State: closed - Opened by Riduidel almost 12 years ago
Labels: bug

#25 - literal values with no type infos should be considered as string

Issue - State: closed - Opened by Riduidel almost 12 years ago

GitHub / Riduidel/gaedo issues and pull requests