Heh no problem. I'll cc the list for you.
So basically propel creates an object to represent each table in a
DB. Foreign key relationships are maintained, and the propel objects
cache the results.
So, in a simple scenario with "Account" and "Transactions", your
"Account" object keeps an i
Would you mind explaining that "indirect property accessing" method,
Andi? Or did you mean avoiding circular references altogether by
having a third "intermediate" layer that would return the respective
object when handed a GUID or something, so that effectively, one of
the partners in the
regarding the actually topic of this thread I'm very interested
in the concept of 'weak references' (as Apple seems to call them),
what '$this->this' is all about, and whether using reference notation
with object variable assignment is even allowed, whether it it makes
a difference and what the fu
Andi Gutmans wrote:
Sorry about that. I think it might be a problem with the server not my
client.
If it persists please let me know.
given what your work has done for me I can't consider it a
problem :-) just thought it was kinda funny.
regarding the actually topic of this thread I'm very in
Sorry about that. I think it might be a problem with the server not my client.
If it persists please let me know.
At 08:37 AM 12/9/2005, Jochem Maas wrote:
Andi - your email client seems to be leaking :-)
Andi Gutmans wrote:
Hi Alan,
Generally speaking, if you create a circular reference (whet
Andi - your email client seems to be leaking :-)
Andi Gutmans wrote:
Hi Alan,
Generally speaking, if you create a circular reference (whether by
reference or by value), then you will have a "memory leak" until the end
of the request. This is not only true for objects (and circular
references
On 12/9/05, Alan Pinstein <[EMAIL PROTECTED]> wrote:
> However, my question, which still remains unanswered, is that I've
> found a way that "seems" to create a weak reference and I'm simply
> asking if what I am doing is condoned or just lucky (and thus a bad
> idea that will probably break in the
Hey,
re: limiting factor I don't completely disagree but then again, in
most cases, it's possible to design the app in a way which resolves
the problem.
As to weak references, you could do weak references in PHP just by
using the indirect property access. Might not be perfect but it's quite do
re: limiting factor I don't completely disagree but then again, in
most cases, it's possible to design the app in a way which resolves
the problem.
Well, this is true, but then it would either:
a) reduce the functionality of the object layer (by eliminating
references to "parent")
b) ad
On Fri, 2005-12-09 at 00:21, Alan Pinstein wrote:
>
> And, if it's just lucky, then what is the solution to the problem? Am
> I just SOL? Is the answer simply that if you *need* to create
> circular references in PHP, then you *must* accept memory leakage?
If you know you have a circular refe
Generally speaking, if you create a circular reference (whether by
reference or by value), then you will have a "memory leak" until
the end of the request. This is not only true for objects (and
circular references might be indirect) but also for arrays.
sure, of course...
This is a side-e
Hi Alan,
Generally speaking, if you create a circular reference (whether by
reference or by value), then you will have a "memory leak" until the
end of the request. This is not only true for objects (and circular
references might be indirect) but also for arrays.
This is a side-effect of refer
My question is closely related to the one discussed on this php-dev
thread:
http://thread.gmane.org/gmane.comp.php.devel/32430
Someone just sent me this link, which I didn't find myself when
searching b/c the searches strip "this" from queries.
Anyway, the question is related to reference
Well I posted there first, and someone helped me believe that & on
objects does indeed legitimately not bump the refcount, but no one
knows about $this->this. And there's another similar thread on the
dev list anyway which was answered usefully: http://
aspn.activestate.com/ASPN/Mail/Message
are you using ph4 or php5?
PHP5
are you setting $this->this yourself or 'is it just there'?
No, I'm not setting it, just reading it (see addChildObject() code
below), if that's what you mean.
-Alan
Alan Pinstein wrote:
Hi all-
I've been trying to avoid circular references in some dat
Antony Dovgal wrote:
On 07.12.2005 18:40, Alan Pinstein wrote:
Hi all-
Please use php-general@lists.php.net for questions regarding development
*in* PHP.
Please stop bashing other people's messages for the sole reason they do
not deal with C code. The question was perfectly relevant.
I don't think PHP-general would be of much help here. After all, his
question was whether this behavior is intentional or not, and if it
can be relied upon in the future. To me, it's an engine thing. And
I'm interested in what the devs can say about this, too.
- David
Am 07.12.2005 um 17
On 07.12.2005 18:40, Alan Pinstein wrote:
Hi all-
Please use php-general@lists.php.net for questions regarding development *in* PHP.
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
are you using ph4 or php5?
are you setting $this->this yourself or 'is it just there'?
Alan Pinstein wrote:
Hi all-
I've been trying to avoid circular references in some data import
scripts and finally figured out how to do it. However, I wanted to ask
you guys to make sure that what I'm do
Hi all-
I've been trying to avoid circular references in some data import
scripts and finally figured out how to do it. However, I wanted to
ask you guys to make sure that what I'm doing is something that's
legit and can be relied on into the future.
Also, please note that I tried searchi
20 matches
Mail list logo
