[TYPO3-project-realty] Install Problem - CREATE TABLE tx_ralty_objects fails

Christophe Stadler discopimp at pornogamy.net
Thu Jul 24 15:26:22 CEST 2008


Hi again,

Techsupport from my hosting company has had an insight:

When you replace "accessible" with "amenable" the table can be created,
however when updating the extension in the extension manager it wants to
rename it back and records still can't be created.

I suppose 'accessible' is a reserved term in 5.1.25-rc

Let me know if this helps, i'm struggling to integrate OpenRealty into typo3
and would much preferr to have everything already integrated :)


On 7/23/08 9:56 PM, in article
mailman.1.1216843016.30482.typo3-project-realty at lists.netfielders.de,
"Christophe Stadler" <discopimp at pornogamy.net> wrote:

> Hi again,
> 
> I'm sorry but i have never used bugzilla, i created an account but i don't
> really know what to do there ... It says:
> 
> Status:      RESOLVED
> Resolution:     WORKSFORME
> 
> Sorry for my ignorance ... I attached a txt file with all the info i could
> find on mysql in my php info page, hope this helps.
> 
> I tried a couple more times on a fresh install of typo3 done with the cpanel
> of my hosting provider, and another one on the same server but installed
> manually, both have the same error when i try to inject the sql i see in the
> backend in the extension installer:
> 
> error : You have an error in your SQL syntax; check the manual that
> corresponds to your MySQL server version for the right syntax to use near
> 'accessible tinyint(3) NOT NULL default '0',
> assisted_living tinyint(3) NOT NULL ' at line 60
> 
> Here is the sql i tried:
> 
> CREATE TABLE tx_realty_objects (
> uid int(11) unsigned NOT NULL auto_increment,
> pid int(11) NOT NULL default '0',
> tstamp int(11) NOT NULL default '0',
> crdate int(11) NOT NULL default '0',
> cruser_id int(11) NOT NULL default '0',
> t3ver_oid int(11) NOT NULL default '0',
> t3ver_id int(11) NOT NULL default '0',
> t3ver_wsid int(11) NOT NULL default '0',
> t3ver_label varchar(30) NOT NULL default '',
> t3ver_state tinyint(4) NOT NULL default '0',
> t3ver_stage tinyint(4) NOT NULL default '0',
> t3ver_count int(11) NOT NULL default '0',
> t3ver_tstamp int(11) NOT NULL default '0',
> t3_origuid int(11) NOT NULL default '0',
> sys_language_uid int(11) NOT NULL default '0',
> l18n_parent int(11) NOT NULL default '0',
> l18n_diffsource mediumblob NOT NULL,
> deleted tinyint(4) NOT NULL default '0',
> hidden tinyint(4) NOT NULL default '0',
> is_dummy_record tinyint(1) unsigned NOT NULL default '0',
> starttime int(11) NOT NULL default '0',
> endtime int(11) NOT NULL default '0',
> object_number tinytext NOT NULL,
> object_type int(11) NOT NULL default '0',
> title tinytext NOT NULL,
> emphasized tinyint(3) NOT NULL default '0',
> street tinytext NOT NULL,
> zip tinytext NOT NULL,
> city int(11) NOT NULL default '0',
> district int(11) NOT NULL default '0',
> number_of_rooms tinytext NOT NULL,
> living_area tinytext NOT NULL,
> total_area tinytext NOT NULL,
> rent_excluding_bills tinytext NOT NULL,
> extra_charges tinytext NOT NULL,
> heating_included tinyint(3) NOT NULL default '0',
> deposit tinytext NOT NULL,
> provision tinytext NOT NULL,
> usable_from tinytext NOT NULL,
> buying_price tinytext NOT NULL,
> year_rent tinytext NOT NULL,
> rented tinyint(3) NOT NULL default '0',
> apartment_type int(11) NOT NULL default '0',
> house_type int(11) NOT NULL default '0',
> floor int(11) NOT NULL default '0',
> floors int(11) NOT NULL default '0',
> bedrooms int(11) NOT NULL default '0',
> bathrooms int(11) NOT NULL default '0',
> heating_type int(11) NOT NULL default '0',
> garage_type int(11) NOT NULL default '0',
> garage_rent tinytext NOT NULL,
> garage_price tinytext NOT NULL,
> pets int(11) NOT NULL default '0',
> construction_year int(11) NOT NULL default '0',
> state int(11) NOT NULL default '0',
> balcony tinyint(3) NOT NULL default '0',
> garden tinyint(3) NOT NULL default '0',
> elevator tinyint(3) NOT NULL default '0',
> accessible tinyint(3) NOT NULL default '0',
> assisted_living tinyint(3) NOT NULL default '0',
> fitted_kitchen tinyint(3) NOT NULL default '0',
> description text NOT NULL,
> equipment text NOT NULL,
> layout tinytext NOT NULL,
> location text NOT NULL,
> misc text NOT NULL,
> details_page tinytext,
> images int(11) NOT NULL default '0',
> employer text NOT NULL,
> openimmo_anid text NOT NULL,
> openimmo_obid text NOT NULL,
> utilization text NOT NULL,
> contact_person text NOT NULL,
> contact_email text NOT NULL,
> PRIMARY KEY (uid),
> KEY parent (pid)
> )
> 
> Server info:
> 
> Mysql: 5.1.25-rc
> Php: 5.2.6
> 
> 
> On 7/23/08 8:04 PM, in article
> mailman.1.1216836289.4768.typo3-project-realty at lists.netfielders.de, "Oliver
> Klee" <typo3-german-02 at oliverklee.de> wrote:
> 
>> Hi Christophe,
>> 
>> Christophe Stadler schrieb:
>>> My provider informed me that it is not possible or sensible to switch of
>>> strict mode. I tried again installing ralty under a frsh install with a
>>> MYSQL5 databse and the same issue appears.
>>> 
>>> I won't have time to bug-report this since i already spent quite a lot of
>>> time trying to get this to work and haven't even been able to try out wether
>>> i want to use this extension.
>> 
>> I cannot reproduce this with MySQL 5.0 using STRICT_ALL_TABLES. However,
>> I've filed a bug report on this issue:
>> <https://bugs.oliverklee.com/show_bug.cgi?id=2024>
>> 
>> If you can get any more information needed to reproduce this issue (e.g.
>> exactly which modes your MySQL installation uses or any other important
>> configuration details), could you please post them to the bug report?
>> 
>> (We need to be able to reproduce this issue first before we can develop
>> and test a fix.)
>> 
>> Thanks again,
>> 
>> 
>> Oliver
> 



More information about the TYPO3-project-realty mailing list