On 28 Aug 2018, at 11:52 am, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com>
wrote:
>
> It does, but remember if you already have multiple transactions, you will
> have to keep track and may have to suspend that many times
I don't think that is true. When you SUSPEND TRANSACTION, the effective
It does, but remember if you already have multiple transactions, you will have
to keep track and may have to suspend that many times
Regards
Chuck
Chuck Miller Voice: (617) 739-0306
Informed
read access on a shared object triggers built-in Use/End use.
in that sense, the speed "penalty" for access is no different to write.
the speed question really boils down to what you do inside Use/End use.
for example, you might do New shared object, New shared collection.
you might do
I prefer to reference the pieces as:
Host - the primary system in which 1 or more components are installed
Component - a library of functions and/or forms which are focused on a specific
task
less confusing :)
and 4D references both of these terms at various points in their documentation
Chip
On 28 Aug 2018, at 6:08 am, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
wrote:
>
> Hey guys - the very issue with the record counter is sketched out in the
> discussion about Suspending Transactions:
>
> http://doc.4d.com/4Dv16/4D/16.3/Suspending-transactions.300-3652126.en.html
>
>
> I
Hi guys,
Thanks for all your suggestions and helpful info.
After considering all these options, I've come up with a simple solution
that seems to work perfectly well, although it hasn't yet been tested
comprehensively.
The important thing is that all record cancellations go through a
Jody,
Yes, that term took a while to get used to…
It is basically just your 4D database that contains all the code, forms, etc
that you are putting into your component.
Components are matrix databases whose files are suffixed either .4db
(interpreted matrix database), .4dc (compiled matrix
Hey guys - the very issue with the record counter is sketched out in the
discussion about Suspending Transactions:
http://doc.4d.com/4Dv16/4D/16.3/Suspending-transactions.300-3652126.en.html
I had missed this - it's quite a feature.
On Mon, Aug 27, 2018 at 7:54 AM Keisuke Miyako via 4D_Tech <
On Aug 27, 2018, at 2:00 PM, John DeSoi wrote:
> I don't know. In some simple tests without any contention from multiple
> processes, both reading and writing took 0 ms.
>
> I did not know Storage was slow until this thread came up. I did not see that
> in the documentation, maybe only
I don't know. In some simple tests without any contention from multiple
processes, both reading and writing took 0 ms.
I did not know Storage was slow until this thread came up. I did not see that
in the documentation, maybe only something you learn about if you go to the
conference. Without
yes :)
it would simplify the code to create a new sequence value,
rather then having to pass the needed info out of the current
transaction/process into a new process, and then transfer it back.
I'll keep this in mind for when I finally get to v16+ :)
On Mon, 27 Aug 2018 14:53:13 +,
Does the speed penalty apply to reading values from Storage, or just to writing
values to Storage?
Thanks,
Keith - CDI
> On Aug 26, 2018, at 8:57 AM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Storage is the best option for interprocess communications if you want to use
>
transactions can be paused since v16
would that help?
http://doc.4d.com/4Dv16/4D/16.3/SUSPEND-TRANSACTION.301-3652123.en.html
> 2018/08/27 23:46、Chip Scheide via 4D_Tech <4d_tech@lists.4d.com>のメール:
> working from inside a transaction requires (as far as I can figure out)
> stepping outside the
there is the catch :)
working from inside a transaction requires (as far as I can figure out)
stepping outside the transaction process and generating the value(s)
then passing the value(s) back into the transaction.
Returning requires the same thing-in reverse.
Chip
On Sat, 25 Aug 2018
Chuck:
That is exactly what we do for our code. Has served us well for all our sites.
We can have 200+ current users on the system, importing records from labs (thus
needing lots of counters quickly), and never noticed a problem with the system.
For those counters we do not wanted to have one
15 matches
Mail list logo
