SqliImport, search if attribute value already exists

Previous topic

Extensions

Next topic

Author	Message
Jérémie Caulier	Tuesday 03 May 2011 12:56:03 am I have a content type that looks like this: myContentType { unique_id: integer title: string ... } I retrieve data from an external data source and want to aggregate them automatically in eZ Publish content tree. But before the import, I want to check if an other object related to "myContenType" not exists with the same unique_id value ... What is the best way to proceed ?
Jérôme Vieilledent	Thursday 05 May 2011 6:16:45 am Hi Jérémie Actually, it's already implemented, native and automatic :). If you use RemoteID, SQLIContent::create() will automatically check if a content already exists with this RemoteID. If this is the case, it will be returned. Then, when you'll publish it, the publisher will go through all the attributes and check if there has been a modification. If this is the case, a new version is created, if not the content is not modified. You can check the doc in the "Simplified content API" part : http://svn.projects.ez.no/sqliimport/trunk/doc/README.txt
Jérémie Caulier	Saturday 07 May 2011 4:12:35 am Thnx, it's a really nice extension !

Author

Message

Jérémie Caulier

Tuesday 03 May 2011 12:56:03 am

I have a content type that looks like this:
myContentType
{
unique_id: integer
title: string
...
}

I retrieve data from an external data source and want to aggregate them automatically in eZ Publish content tree.

But before the import, I want to check if an other object related to "myContenType" not exists with the same unique_id value ...

What is the best way to proceed ?

Jérôme Vieilledent

Thursday 05 May 2011 6:16:45 am

Hi Jérémie

Actually, it's already implemented, native and automatic :).

If you use RemoteID, SQLIContent::create() will automatically check if a content already exists with this RemoteID. If this is the case, it will be returned. Then, when you'll publish it, the publisher will go through all the attributes and check if there has been a modification. If this is the case, a new version is created, if not the content is not modified.

You can check the doc in the "Simplified content API" part : http://svn.projects.ez.no/sqliimport/trunk/doc/README.txt

Jérémie Caulier

Saturday 07 May 2011 4:12:35 am

Thnx, it's a really nice extension !

eZ debug

Timing:	Jan 30 2025 00:53:22
Script start
Timing:	Jan 30 2025 00:53:22
Module start 'layout'
Timing:	Jan 30 2025 00:53:22
Module start 'content'
Timing:	Jan 30 2025 00:53:22
Module end 'content'
Timing:	Jan 30 2025 00:53:22
Script end

Main resources:

Total runtime	0.0412 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0071	588.2813	151.2266
Module start 'layout'	0.0071	0.0032	739.5078	36.6875
Module start 'content'	0.0103	0.0292	776.1953	90.3906
Module end 'content'	0.0396	0.0015	866.5859	29.9766
Script end	0.0411		896.5625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	6.7046	14	0.0002
Check MTime	0.0011	2.7275	14	0.0001
Mysql Total
Database connection	0.0013	3.1197	1	0.0013
Mysqli_queries	0.0029	6.9439	3	0.0010
Looping result	0.0000	0.0487	1	0.0000
Template Total	0.0010	2.6	1	0.0010
Template load	0.0008	2.0456	1	0.0008
Template processing	0.0002	0.4930	1	0.0002
Override
Cache load	0.0006	1.3927	1	0.0006
General
dbfile	0.0182	44.2304	8	0.0023
String conversion	0.0000	0.0238	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs