GoZync4

Transactional

GoZync4.Transactional History

Hide minor edits - Show changes to output

March 28, 2014, at 09:08 PM by 50.132.84.245 -
Added lines 18-19:

Why "import records" doesn't work: %newwin% [[https://www.geistinteractive.com/2014/03/21/syncing-filemaker-transactions/ | transactions and syncing.]]
March 04, 2014, at 04:14 PM by 50.132.84.245 -
Deleted lines 16-18:
Wikipedia definition: %newwin%
[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]

Changed lines 20-23 from:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]] and %newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions]].
to:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]] and %newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions]].

Wikipedia definition: %newwin%
[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
March 04, 2014, at 04:13 PM by 50.132.84.245 -
Changed lines 20-21 from:
The FileMaker Transactions reference page: %newwin% [[https://www.geistinteractive.com/filemaker-transactions/ | https://www.geistinteractive.com/filemaker-transactions]]
to:
The %newwin% [[https://www.geistinteractive.com/filemaker-transactions/ | FileMaker Transactions reference page]]
Changed lines 23-25 from:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]

%newwin%
[[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions]]
to:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]] and %newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions]].
March 04, 2014, at 04:13 PM by 50.132.84.245 -
Changed lines 18-19 from:
\\ [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
to:
[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
Changed line 23 from:
\\ %newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]
to:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]
March 04, 2014, at 04:12 PM by 50.132.84.245 -
Changed lines 17-18 from:
Wikipedia definition: %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
to:
Wikipedia definition: %newwin% 
\\
[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
Changed line 23 from:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]
to:
\\ %newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]
March 04, 2014, at 04:12 PM by 50.132.84.245 -
Changed line 17 from:
Wikipedia definition:[[<<]] %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
to:
Wikipedia definition: %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
March 04, 2014, at 04:11 PM by 50.132.84.245 -
Changed line 17 from:
Wikipedia definition: %newwin% \\[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
to:
Wikipedia definition:[[<<]] %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
March 04, 2014, at 04:11 PM by 50.132.84.245 -
March 04, 2014, at 04:11 PM by 50.132.84.245 -
Changed lines 17-18 from:
Wikipedia definition: %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
to:
Wikipedia definition: %newwin% \\[[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]
Changed lines 22-24 from:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions/]]

%newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions/]]
to:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions]]

%newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions]]
March 04, 2014, at 04:11 PM by 50.132.84.245 -
Changed lines 19-21 from:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/]]

%newwin% [[http:
//www.geistinteractive.com/2010/04/21/inventory-transactions/ | http://www.geistinteractive.com/2010/04/21/inventory-transactions/]]
to:
The FileMaker Transactions reference page: %newwin% [[https://www.geistinteractive.com/filemaker-transactions/ | https://www.geistinteractive.com/filemaker-transactions]]

Older Articles
:
%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | filemaker-go-and-transactions/]]

%newwin% [[http:
//www.geistinteractive.com/2010/04/21/inventory-transactions/ | inventory-transactions/]]
June 30, 2013, at 08:06 PM by 50.132.84.245 -
Changed lines 3-8 from:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph how many tables that package spans. Transactions can also include any scripted edits that have to happen on either the mobile or hosted side scripts like notifications or logging.

All of that goes with the record,
or none of it goes. Outside of a transaction, some or all of that could happen per record, per sync.

When you have a shaky connection, or turn off your device mid-sync
, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
to:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph how many tables that package spans using the "required" column on GoZyncHosted's configuration tab. Transactions can also include any additional set fields that have to happen on either the mobile or hosted side--things like notifications or [[checking out records | checkout]].

All
of that goes with the record, or none of it goes. Without transactions, some or all of that could happen per record, per sync. Fo example, when you have a shaky connection, or turn off your device mid-sync, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification anyway.
December 10, 2012, at 10:34 PM by cm - clarifying paragraph and edits
Changed lines 3-4 from:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (you, as the developer, control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
to:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all its related records, are bound together in an indivisible package. You, as the developer, control how far across the graph how many tables that package spans. Transactions can also include any scripted edits that have to happen on either the mobile or hosted side scripts like notifications or logging.
Changed lines 7-8 from:
When you have a shaky connection, or turn off your device mid sync. You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
to:
When you have a shaky connection, or turn off your device mid-sync, you could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
Changed lines 11-12 from:
Transactions are what let us say that when you see "uploaded" on a zynced record in your mobile file, you '''know''' that record made it to the host / server.
to:
GoZync eliminates the possibility of incomplete syncs by enclosing all of the data within a transaction envelope. If a transaction completes a Zync, it's complete. If it fails because of connection problems, it leaves the data untouched.

Transactions are what let us say that when you see "uploaded" on a Zynced
record in your mobile file, you '''know''' that record made it to the host / server.
Changed lines 17-18 from:
Todd Geist, co-author of GoZync pioneered the concept of transactions for FileMaker Pro. Read more on this here:
to:
Todd Geist, co-author of GoZync, pioneered the concept of transactions for FileMaker Pro. Read more on this here:
Changed line 23 from:
%newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | http://www.geistinteractive.com/2010/04/21/inventory-transactions/]]
to:
%newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | http://www.geistinteractive.com/2010/04/21/inventory-transactions/]]
July 15, 2012, at 10:57 PM by 63.138.103.86 -
Changed lines 5-10 from:
All of that goes with the record, or none of it goes.

Outside
of a transaction, some or all of that could happen per record, per sync.

You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
to:
All of that goes with the record, or none of it goes. Outside of a transaction, some or all of that could happen per record, per sync.

When you have a shaky connection, or turn off your device mid sync. You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.
July 15, 2012, at 10:56 PM by 63.138.103.86 -
Changed lines 3-4 from:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (devs control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
to:
A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (you, as the developer, control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.
July 02, 2012, at 04:59 PM by 50.132.84.245 -
Added lines 13-14:
Transactions are what let us say that when you see "uploaded" on a zynced record in your mobile file, you '''know''' that record made it to the host / server.
July 02, 2012, at 04:56 PM by 50.132.84.245 -
Added lines 1-21:
!! What does it mean that GoZync is "transactional"?

A transaction means that everything associated with a record stays with the record. In a sync context that means the record, and all it's related records, are bound together in an indivisible package (devs control how far across the graph--how many tables--that package spans) which can also include any scripted edits that have to happen on either the mobile or hosted side: scripted things like notifications or logging.

All of that goes with the record, or none of it goes.

Outside of a transaction, some or all of that could happen per record, per sync.

You could sync an invoice, but not its line items. Or sync the invoice and its line items, but not send the notification. Or sync the invoice, fail the line items, and the send the notification.

While you'll see this on FileMaker networked solutions sometimes (usually as incomplete records, or totals that don't match) you see it much more often in distributed (Go) solutions where disconnect and record lock can be common.

!! Learn more about transactions.

Todd Geist, co-author of GoZync pioneered the concept of transactions for FileMaker Pro. Read more on this here:

Wikipedia definition: %newwin% [[http://en.wikipedia.org/wiki/Database_transaction | http://en.wikipedia.org/wiki/Database_transaction]]

%newwin% [[http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/ | http://www.geistinteractive.com/2010/07/21/filemaker-go-and-transactions/]]

%newwin% [[http://www.geistinteractive.com/2010/04/21/inventory-transactions/ | http://www.geistinteractive.com/2010/04/21/inventory-transactions/]]
(855) SEEDCODE
support@seedcode.com
Follow us: