Smalltalk › Frameworks & Tools › GLORP

Pharo DatabaseField new disabled

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Brad Selfridge

Pharo DatabaseField new disabled

I'm curious as to why the "DatabaseField new" method has been disabled/overridden? Is this strategic in any way?

I'm working on a Pharo Glorp GUI and am kind of needing the "new" method to be usable.

Brad Selfridge

Esteban A. Maringolo

Re: Pharo DatabaseField new disabled

You can always use #basicNew, hopefully followed by #initialize, but
not strictly necessary if you are doing a lot of internal state
manipulation and can handle "uninitialized" object state.

Best regards,
Esteban A. Maringolo

2016-10-13 8:17 GMT-03:00 Brad Selfridge <[hidden email]>:

> I'm curious as to why the "DatabaseField new" method has been
> disabled/overridden? Is this strategic in any way?
>
> I'm working on a Pharo Glorp GUI and am kind of needing the "new" method to
> be usable.
>
>
>
> -----
> Brad Selfridge
> --
> View this message in context: http://forum.world.st/Pharo-DatabaseField-new-disabled-tp4918800.html
> Sent from the GLORP mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups "glorp-group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> Visit this group at https://groups.google.com/group/glorp-group.
> For more options, visit https://groups.google.com/d/optout.

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

Alan Knight

Re: Pharo DatabaseField new disabled

Depending what you're trying to do, you could also use some kind of a builder pattern that has a field representation that won't be turned into a real field until it's saved, when it has enough information. Or you could use named:type: with a default name and type and change them later.

On Thu, Oct 13, 2016 at 7:09 AM Esteban A. Maringolo <[hidden email]> wrote:

You can always use #basicNew, hopefully followed by #initialize, but
not strictly necessary if you are doing a lot of internal state
manipulation and can handle "uninitialized" object state.

Best regards,
Esteban A. Maringolo

2016-10-13 8:17 GMT-03:00 Brad Selfridge <[hidden email]>:
> I'm curious as to why the "DatabaseField new" method has been
> disabled/overridden? Is this strategic in any way?
>
> I'm working on a Pharo Glorp GUI and am kind of needing the "new" method to
> be usable.
>
>
>
> -----
> Brad Selfridge
> --
> View this message in context: http://forum.world.st/Pharo-DatabaseField-new-disabled-tp4918800.html
> Sent from the GLORP mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups "glorp-group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> Visit this group at https://groups.google.com/group/glorp-group.
> For more options, visit https://groups.google.com/d/optout.

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