Yes.. smalltalk doesn’t impose a whole lot of style limitations on the
developer, and most of the code i run into is very high quality.. so, using all
the available code, you’re really just learning good practices from a bunch of
smart people…
the language is really inconsequential..
On Februa
> Am 01.02.2017 um 17:02 schrieb sergio ruiz :
>
> Got it..
>
> Smalltalk is one language where it ALWAYS seems that there is a more clever
> way to do anything than the way i am doing it..
>
> I’ll try this..
>
Don't worry. That is the experience we all had (and have). You look for a
metho
Got it..
Smalltalk is one language where it ALWAYS seems that there is a more clever way
to do anything than the way i am doing it..
I’ll try this..
Thanks!
On February 1, 2017 at 10:43:36 AM, Norbert Hartl (norb...@hartl.name) wrote:
MyClass selectOne: {
'_id' -> (OID value: 16r) } asDictio
> Am 01.02.2017 um 16:11 schrieb sergio ruiz :
>
> hmmm.. can you query for an object with that voyageId?
Sure. I don't know if there is a more clever way to do but this will work in
any case
MyClass selectOne: {
'_id' -> (OID value: 16r) } asDictionary
Norbert
>
> On February 1, 20
hmmm.. can you query for an object with that voyageId?
On February 1, 2017 at 9:37:43 AM, Norbert Hartl (norb...@hartl.name) wrote:
You can ask every voyage object for its id. Just do
anObject voyageId
you get an OID object which you can ask for its #value to get the numeric id.
Norbert
Perfect! this is what i needed.. i don’t want to manage two sets of IDs..
Thanks!
On February 1, 2017 at 9:37:43 AM, Norbert Hartl (norb...@hartl.name) wrote:
You can ask every voyage object for its id. Just do
anObject voyageId
you get an OID object which you can ask for its #value to get th
> Am 01.02.2017 um 15:25 schrieb sergio ruiz :
>
> Hi, all..
>
> I am working on a Teapot REST interface, and am getting ready to implement
> the create, read, and update methods for the objects, and I need a way to
> refer to the objects. I figured that since Voyage was already creating _id
Hi, all..
I am working on a Teapot REST interface, and am getting ready to implement the
create, read, and update methods for the objects, and I need a way to refer to
the objects. I figured that since Voyage was already creating _id through
MongoDB, I could just pass that on when I retrieved t