Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: [propel] Duplicate primaryKey in column does not through error until insert-sql

propel
Discussion topic

Hide all messages in topic

All messages in topic

Re: [propel] Duplicate primaryKey in column does not through error until insert-sql

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-12 13:25:27 PDT
Message Hi Matt,

>
> I've noticed a trend in the propel where problems that will occur in
> insert-sql are not shown as errors/warnings during the phing build
> phase. Is this just missing error handling or is there some other
> reason?

Well if you mean that you don't see the errors until you run the
'insert-sql' target, then yeah -- this is known. The SQL isn't actually
run against the database until you run 'insert-sql', so some things (like
the previous INDEX()) issue won't be caught until then.

However, there are some schema errors that should be caught before hand.
>From the subject of the message, it sounds like the problem you're
referring to (duplicate pkey) could/should be caught. There is a method
that is run at the end of loading the schema (I believe in
phing/PropelDataModelTask.php) that should throw exceptions on obvious
errors. We just need to add other tests in that method.

Hans

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

[propel] Duplicate primaryKey in column does not through error until insert-sql

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-12 13:16:02 PDT
Message Hello everyone,

I've noticed a trend in the propel where problems that will occur in
insert-sql are not shown as errors/warnings during the phing build
phase. Is this just missing error handling or is there some other
reason?

Thanks,

Matt

On Apr 12, 2004, at 15:42, Hans Lellelid wrote:

> Hi Matt & Denny,
>
> I applied the fix below to the foreignkey.tpl template. If you update
> from CVS this should be there.
>
> I ended up using Matt's code w/o modification:
>
>> <?php foreach ($table->getForeignKeys() as $fk) { ?>
>> INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
>> FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
>> <?php echo $fk->getForeignTableName() ?> (<?php echo
>> $fk->getForeignColumnNames() ?>),
>> <?php } ?>
>
> since MySQL/InnoDB does not complain if you define an index more than
> once. That made it easier than needing to check to see whether index
> already existed -- and I wasn't completely sure what would happen if
> column was part of another multi-column index, etc. We'll keep it like
> this unless someone has trouble with it.
>
> Thanks,
> Hans
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

[propel] Fix applied -- Re: [propel] Many-to-Many Relationship Problem Fix

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-12 12:42:38 PDT
Message Hi Matt & Denny,

I applied the fix below to the foreignkey.tpl template. If you update
from CVS this should be there.

I ended up using Matt's code w/o modification:

> <?php foreach ($table->getForeignKeys() as $fk) { ?>
> INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
> FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
> <?php echo $fk->getForeignTableName() ?> (<?php echo
> $fk->getForeignColumnNames() ?>),
> <?php } ?>

since MySQL/InnoDB does not complain if you define an index more than
once. That made it easier than needing to check to see whether index
already existed -- and I wasn't completely sure what would happen if
column was part of another multi-column index, etc. We'll keep it like
this unless someone has trouble with it.

Thanks,
Hans

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

Re: [propel] Many-to-Many Relationship Problem Fix

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-12 12:34:14 PDT
Message Hi Matt--

Thanks for the code sample. This is almost 100% right. The only thing we
need to check is whether the col was already specified (in the schama) as
being indexed. I'll do this now & should have it ready for you to test in
a few minutes.

Thanks-
Hans

> I did this to propel/templates/sql​/base/mysql/foreignk​ey.tpl to make it
> work:
>
> <?php foreach ($table->getForeignKeys() as $fk) { ?>
> INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
> FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
> <?php echo $fk->getForeignTableName() ?> (<?php echo
> $fk->getForeignColumnNames() ?>),
> <?php } ?>
>
> Notice the added INDEX line. I don't know if that will work in every
> case but at least create-db now works again.
>
> I didn't commit this to CVS because I don't understand foreign keys
> well yet.
>
> Hope that helps : )
>
> - Matt
>
> On Apr 12, 2004, at 15:20, Matthew B. Hershberger wrote:
>
>> Hans,
>>
>> Your description exactly describes my problem. The manual and examples
>> say it should work but I wanted to make sure I wasn't doing something
>> wrong.
>>
>> Thanks for your help,
>>
>> Matt
>>
>> On Apr 12, 2004, at 14:53, Hans Lellelid wrote:
>>
>>> Hi Matt,
>>>
>>> Yes, I believe this is a known issue (and in the bug tracker for me to
>>> tackle). I believe the error you got had something to do with lack of
>>> indexes on the fkey constraints, correct? This seems to be a
>>> mysql/innodb
>>> issue -- well, not an issue, just a difference between mysql and
>>> other dbs
>>> that use fkeys. This should be no problem to fix, since we have
>>> individual templates for all the db systems. I just haven't done it
>>> yet
>>> :) I think there's even some code on the dev list.... I'll try to get
>>> this done ASAP.
>>>
>>> If I'm wrong about the problem, let me know.
>>>
>>> Thanks,
>>> Hans
>>>
>>>> Hello,
>>>>
>>>> I have never used Foreign Keys before and on Saturday I found a
>>>> problem. I'm not sure if there is a problem in propel or maybe I
>>>> missed
>>>> something in my schema file. The schema is attached below.
>>>>
>>>> I created the first query after seeing a working example in the mysql
>>>> manual.
>>>>
>>>> The following CREATE TABLE works:
>>>> CREATE TABLE account_priv_ref(
>>>>
>>>> account INTEGER NOT NULL ,
>>>>
>>>> privilege INTEGER NOT NULL ,
>>>>
>>>> PRIMARY KEY(account,privilege),
>>>> INDEX(account),
>>>> FOREIGN KEY (account) REFERENCES account (id),
>>>> INDEX(privilege),
>>>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>>>
>>>> This query was created by the propel build file.
>>>> This CREATE TABLE fails: (errno: 150 [foreign-key problem])
>>>> CREATE TABLE account_priv_ref(
>>>>
>>>> account INTEGER NOT NULL ,
>>>>
>>>> privilege INTEGER NOT NULL ,
>>>>
>>>> PRIMARY KEY(account,privilege),
>>>> FOREIGN KEY (account) REFERENCES account (id),
>>>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>>>
>>>> Here are the other two related tables:
>>>> CREATE TABLE account(
>>>>
>>>> id INTEGER NOT NULL ,
>>>>
>>>> firstName VARCHAR(30) NOT NULL ,
>>>>
>>>> lastName VARCHAR(30) NOT NULL ,
>>>>
>>>> email VARCHAR(100) ,
>>>>
>>>> username VARCHAR(30) NOT NULL ,
>>>>
>>>> password VARCHAR(30) NOT NULL ,
>>>>
>>>> externalId VARCHAR(30) ,
>>>>
>>>> PRIMARY KEY(id)) Type=InnoDB;
>>>>
>>>> CREATE TABLE privilege(
>>>>
>>>> id INTEGER NOT NULL ,
>>>>
>>>> name VARCHAR(50) NOT NULL ,
>>>>
>>>> namepsace VARCHAR(200) NOT NULL ,
>>>>
>>>> PRIMARY KEY(id)) Type=InnoDB;
>>>>
>>>> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd
>>>> 4.9.
>>>>
>>>> Schema
>>>> ---
>>>> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
>>>> <!DOCTYPE database SYSTEM "../dtd/database.dtd">
>>>>
>>>> <database name="athena" defaultIdMethod="native">
>>>> <table name="account" description="User Table">
>>>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>>>> description="id" />
>>>> <column name="firstName" required="true" type="VARCHAR" size="30"
>>>> description="First Name of User" />
>>>> <column name="lastName" required="true" type="VARCHAR" size="30"
>>>> description="Last Name of User" />
>>>> <column name="email" required="false" type="VARCHAR" size="100"
>>>> description="Email Address of User" />
>>>> <column name="username" required="true" type="VARCHAR" size="30"
>>>> description="Account username" />
>>>> <column name="password" required="true" type="VARCHAR" size="30"
>>>> description="Account password" />
>>>> <column name="externalId" required="false" type="VARCHAR" size="30"
>>>> description="External Account Id" />
>>>> </table>
>>>>
>>>> <table name="privilege" description="List of all Privileges">
>>>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>>>> description="id" />
>>>> <column name="name" required="true" type="VARCHAR" size="50"
>>>> description="Name of Privilege" />
>>>> <column name="namepsace" required="true" type="VARCHAR" size="200"
>>>> description="Namespace the privilege resides in" />
>>>> </table>
>>>>
>>>> <table name="account_priv_ref" description="Maps Accounts to
>>>> Available
>>>> Privileges" />
>>>> <column name="account" type="INTEGER" required="true"
>>>> primaryKey="true"
>>>> />
>>>> <column name="privilege" type="INTEGER" required="true"
>>>> primaryKey="true" />
>>>> <foreign-key foreignTable="account">
>>>> <reference local="account" foreign="id"/>
>>>> </foreign-key>
>>>> <foreign-key foreignTable="privilege">
>>>> <reference local="privilege" foreign="id"/>
>>>> </foreign-key>
>>>> </table>
>>>>
>>>> </database>
>>>>
>>>> Thanks,
>>>>
>>>> Matt
>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
>>> For additional commands, e-mail: users-help at propel dot tigris dot org
>>>
>>>
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
>> For additional commands, e-mail: users-help at propel dot tigris dot org
>>
>>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

RE: [propel] Many-to-Many Relationship Problem

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-12 12:31:33 PDT
Message Hi Denny,

No, I'm glad you sent the email! :) It just means that this needs to get
fixed asap. What are you people doing using MySQL w/ foreign keys? :)
I'll try to get that issue fixed today. I'll send a note to this list
when I've fixed it. In the short-term, you can just tweak your generated
SQL files, adding the INDEX() for each fkey column.

This isn't a hard template fix, just need to make sure it takes into
consideration possibility that a fkey column was already specified as an
index, etc.

Thanks,
Hans


> OK... obviously I'm an idiot. :)
> I just sent an email complaining about this very thing
> RIGHT AFTER I read through it.
>
> <sigh>
>
> -----Original Message-----
> From: Hans Lellelid [mailto:hans at velum dot net]
> Sent: Monday, April 12, 2004 2:54 PM
> To: users at propel dot tigris dot org
> Subject: Re: [propel] Many-to-Many Relationship Problem
>
>
> Hi Matt,
>
> Yes, I believe this is a known issue (and in the bug tracker for me to
> tackle). I believe the error you got had something to do with lack of
> indexes on the fkey constraints, correct? This seems to be a
> mysql/innodb issue -- well, not an issue, just a difference between
> mysql and other dbs that use fkeys. This should be no problem to fix,
> since we have individual templates for all the db systems. I just
> haven't done it yet
> :) I think there's even some code on the dev list.... I'll try to get
> this done ASAP.
>
> If I'm wrong about the problem, let me know.
>
> Thanks,
> Hans
>
>> Hello,
>>
>> I have never used Foreign Keys before and on Saturday I found a
>> problem. I'm not sure if there is a problem in propel or maybe I
>> missed something in my schema file. The schema is attached below.
>>
>> I created the first query after seeing a working example in the mysql
>> manual.
>>
>> The following CREATE TABLE works:
>> CREATE TABLE account_priv_ref(
>>
>> account INTEGER NOT NULL ,
>>
>> privilege INTEGER NOT NULL ,
>>
>> PRIMARY KEY(account,privilege),
>> INDEX(account),
>> FOREIGN KEY (account) REFERENCES account (id),
>> INDEX(privilege),
>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>
>> This query was created by the propel build file.
>> This CREATE TABLE fails: (errno: 150 [foreign-key problem]) CREATE
>> TABLE account_priv_ref(
>>
>> account INTEGER NOT NULL ,
>>
>> privilege INTEGER NOT NULL ,
>>
>> PRIMARY KEY(account,privilege),
>> FOREIGN KEY (account) REFERENCES account (id),
>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>
>> Here are the other two related tables:
>> CREATE TABLE account(
>>
>> id INTEGER NOT NULL ,
>>
>> firstName VARCHAR(30) NOT NULL ,
>>
>> lastName VARCHAR(30) NOT NULL ,
>>
>> email VARCHAR(100) ,
>>
>> username VARCHAR(30) NOT NULL ,
>>
>> password VARCHAR(30) NOT NULL ,
>>
>> externalId VARCHAR(30) ,
>>
>> PRIMARY KEY(id)) Type=InnoDB;
>>
>> CREATE TABLE privilege(
>>
>> id INTEGER NOT NULL ,
>>
>> name VARCHAR(50) NOT NULL ,
>>
>> namepsace VARCHAR(200) NOT NULL ,
>>
>> PRIMARY KEY(id)) Type=InnoDB;
>>
>> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.
>>
>> Schema
>> ---
>> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> <!DOCTYPE
>> database SYSTEM "../dtd/database.dtd">
>>
>> <database name="athena" defaultIdMethod="native">
>> <table name="account" description="User Table">
>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>> description="id" /> <column name="firstName" required="true"
>> type="VARCHAR" size="30" description="First Name of User" />
>> <column name="lastName" required="true" type="VARCHAR" size="30"
>> description="Last Name of User" />
>> <column name="email" required="false" type="VARCHAR" size="100"
>> description="Email Address of User" />
>> <column name="username" required="true" type="VARCHAR" size="30"
>> description="Account username" />
>> <column name="password" required="true" type="VARCHAR" size="30"
>> description="Account password" />
>> <column name="externalId" required="false" type="VARCHAR" size="30"
>> description="External Account Id" />
>> </table>
>>
>> <table name="privilege" description="List of all Privileges"> <column
>> name="id" required="true" primaryKey="true" type="INTEGER"
>> description="id" /> <column name="name" required="true" type="VARCHAR"
>
>> size="50" description="Name of Privilege" />
>> <column name="namepsace" required="true" type="VARCHAR" size="200"
>> description="Namespace the privilege resides in" />
>> </table>
>>
>> <table name="account_priv_ref" description="Maps Accounts to Available
>
>> Privileges" /> <column name="account" type="INTEGER" required="true"
>> primaryKey="true" />
>> <column name="privilege" type="INTEGER" required="true"
>> primaryKey="true" />
>> <foreign-key foreignTable="account">
>> <reference local="account" foreign="id"/>
>> </foreign-key>
>> <foreign-key foreignTable="privilege">
>> <reference local="privilege" foreign="id"/>
>> </foreign-key>
>> </table>
>>
>> </database>
>>
>> Thanks,
>>
>> Matt
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

[propel] Many-to-Many Relationship Problem Fix

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-12 12:31:19 PDT
Message Hans,

I did this to propel/templates/sql​/base/mysql/foreignk​ey.tpl to make it
work:

<?php foreach ($table->getForeignKeys() as $fk) { ?>
     INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
     FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
<?php echo $fk->getForeignTableName() ?> (<?php echo
$fk->getForeignColumnNames() ?>),
<?php } ?>

Notice the added INDEX line. I don't know if that will work in every
case but at least create-db now works again.

  I didn't commit this to CVS because I don't understand foreign keys
well yet.

Hope that helps : )

- Matt

On Apr 12, 2004, at 15:20, Matthew B. Hershberger wrote:

> Hans,
>
> Your description exactly describes my problem. The manual and examples
> say it should work but I wanted to make sure I wasn't doing something
> wrong.
>
> Thanks for your help,
>
> Matt
>
> On Apr 12, 2004, at 14:53, Hans Lellelid wrote:
>
>> Hi Matt,
>>
>> Yes, I believe this is a known issue (and in the bug tracker for me to
>> tackle). I believe the error you got had something to do with lack of
>> indexes on the fkey constraints, correct? This seems to be a
>> mysql/innodb
>> issue -- well, not an issue, just a difference between mysql and
>> other dbs
>> that use fkeys. This should be no problem to fix, since we have
>> individual templates for all the db systems. I just haven't done it
>> yet
>> :) I think there's even some code on the dev list.... I'll try to get
>> this done ASAP.
>>
>> If I'm wrong about the problem, let me know.
>>
>> Thanks,
>> Hans
>>
>>> Hello,
>>>
>>> I have never used Foreign Keys before and on Saturday I found a
>>> problem. I'm not sure if there is a problem in propel or maybe I
>>> missed
>>> something in my schema file. The schema is attached below.
>>>
>>> I created the first query after seeing a working example in the mysql
>>> manual.
>>>
>>> The following CREATE TABLE works:
>>> CREATE TABLE account_priv_ref(
>>>
>>> account INTEGER NOT NULL ,
>>>
>>> privilege INTEGER NOT NULL ,
>>>
>>> PRIMARY KEY(account,privilege),
>>> INDEX(account),
>>> FOREIGN KEY (account) REFERENCES account (id),
>>> INDEX(privilege),
>>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>>
>>> This query was created by the propel build file.
>>> This CREATE TABLE fails: (errno: 150 [foreign-key problem])
>>> CREATE TABLE account_priv_ref(
>>>
>>> account INTEGER NOT NULL ,
>>>
>>> privilege INTEGER NOT NULL ,
>>>
>>> PRIMARY KEY(account,privilege),
>>> FOREIGN KEY (account) REFERENCES account (id),
>>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>>
>>> Here are the other two related tables:
>>> CREATE TABLE account(
>>>
>>> id INTEGER NOT NULL ,
>>>
>>> firstName VARCHAR(30) NOT NULL ,
>>>
>>> lastName VARCHAR(30) NOT NULL ,
>>>
>>> email VARCHAR(100) ,
>>>
>>> username VARCHAR(30) NOT NULL ,
>>>
>>> password VARCHAR(30) NOT NULL ,
>>>
>>> externalId VARCHAR(30) ,
>>>
>>> PRIMARY KEY(id)) Type=InnoDB;
>>>
>>> CREATE TABLE privilege(
>>>
>>> id INTEGER NOT NULL ,
>>>
>>> name VARCHAR(50) NOT NULL ,
>>>
>>> namepsace VARCHAR(200) NOT NULL ,
>>>
>>> PRIMARY KEY(id)) Type=InnoDB;
>>>
>>> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd
>>> 4.9.
>>>
>>> Schema
>>> ---
>>> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
>>> <!DOCTYPE database SYSTEM "../dtd/database.dtd">
>>>
>>> <database name="athena" defaultIdMethod="native">
>>> <table name="account" description="User Table">
>>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>>> description="id" />
>>> <column name="firstName" required="true" type="VARCHAR" size="30"
>>> description="First Name of User" />
>>> <column name="lastName" required="true" type="VARCHAR" size="30"
>>> description="Last Name of User" />
>>> <column name="email" required="false" type="VARCHAR" size="100"
>>> description="Email Address of User" />
>>> <column name="username" required="true" type="VARCHAR" size="30"
>>> description="Account username" />
>>> <column name="password" required="true" type="VARCHAR" size="30"
>>> description="Account password" />
>>> <column name="externalId" required="false" type="VARCHAR" size="30"
>>> description="External Account Id" />
>>> </table>
>>>
>>> <table name="privilege" description="List of all Privileges">
>>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>>> description="id" />
>>> <column name="name" required="true" type="VARCHAR" size="50"
>>> description="Name of Privilege" />
>>> <column name="namepsace" required="true" type="VARCHAR" size="200"
>>> description="Namespace the privilege resides in" />
>>> </table>
>>>
>>> <table name="account_priv_ref" description="Maps Accounts to
>>> Available
>>> Privileges" />
>>> <column name="account" type="INTEGER" required="true"
>>> primaryKey="true"
>>> />
>>> <column name="privilege" type="INTEGER" required="true"
>>> primaryKey="true" />
>>> <foreign-key foreignTable="account">
>>> <reference local="account" foreign="id"/>
>>> </foreign-key>
>>> <foreign-key foreignTable="privilege">
>>> <reference local="privilege" foreign="id"/>
>>> </foreign-key>
>>> </table>
>>>
>>> </database>
>>>
>>> Thanks,
>>>
>>> Matt
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
>> For additional commands, e-mail: users-help at propel dot tigris dot org
>>
>>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

RE: [propel] Many-to-Many Relationship Problem

Reply

Author "Denny H dot Shimkoski" <dhs at hamfish dot org>
Full name "Denny H dot Shimkoski" <dhs at hamfish dot org>
Date 2004-04-12 12:27:38 PDT
Message This seems to work for me...

Edit /propel/templates/sq​l/base/mysql/foreign​key.tpl

Changed it to...

<?php foreach ($table->getForeignKeys() as $fk) { ?>
    INDEX (<?php echo $fk->getLocalCol​umnNames()?>),
    FOREIGN KEY (<?php echo $fk->getLocalCol​umnNames()?>) REFERENCES
<?php echo $fk->getForeignTableName() ?> (<?php echo
$fk->getForeignColumnNames() ?>),
<?php } ?>

BAM! Works.

Denny

-----Original Message-----
From: Hans Lellelid [mailto:hans at velum dot net]
Sent: Monday, April 12, 2004 2:54 PM
To: users at propel dot tigris dot org
Subject: Re: [propel] Many-to-Many Relationship Problem


Hi Matt,

Yes, I believe this is a known issue (and in the bug tracker for me to
tackle). I believe the error you got had something to do with lack of
indexes on the fkey constraints, correct? This seems to be a
mysql/innodb issue -- well, not an issue, just a difference between
mysql and other dbs that use fkeys. This should be no problem to fix,
since we have individual templates for all the db systems. I just
haven't done it yet
:) I think there's even some code on the dev list.... I'll try to get
this done ASAP.

If I'm wrong about the problem, let me know.

Thanks,
Hans

> Hello,
>
> I have never used Foreign Keys before and on Saturday I found a
> problem. I'm not sure if there is a problem in propel or maybe I
> missed something in my schema file. The schema is attached below.
>
> I created the first query after seeing a working example in the mysql
> manual.
>
> The following CREATE TABLE works:
> CREATE TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> INDEX(account),
> FOREIGN KEY (account) REFERENCES account (id),
> INDEX(privilege),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> This query was created by the propel build file.
> This CREATE TABLE fails: (errno: 150 [foreign-key problem]) CREATE
> TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> FOREIGN KEY (account) REFERENCES account (id),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> Here are the other two related tables:
> CREATE TABLE account(
>
> id INTEGER NOT NULL ,
>
> firstName VARCHAR(30) NOT NULL ,
>
> lastName VARCHAR(30) NOT NULL ,
>
> email VARCHAR(100) ,
>
> username VARCHAR(30) NOT NULL ,
>
> password VARCHAR(30) NOT NULL ,
>
> externalId VARCHAR(30) ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> CREATE TABLE privilege(
>
> id INTEGER NOT NULL ,
>
> name VARCHAR(50) NOT NULL ,
>
> namepsace VARCHAR(200) NOT NULL ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.
>
> Schema
> ---
> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> <!DOCTYPE
> database SYSTEM "../dtd/database.dtd">
>
> <database name="athena" defaultIdMethod="native">
> <table name="account" description="User Table">
> <column name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" /> <column name="firstName" required="true"
> type="VARCHAR" size="30" description="First Name of User" />
> <column name="lastName" required="true" type="VARCHAR" size="30"
> description="Last Name of User" />
> <column name="email" required="false" type="VARCHAR" size="100"
> description="Email Address of User" />
> <column name="username" required="true" type="VARCHAR" size="30"
> description="Account username" />
> <column name="password" required="true" type="VARCHAR" size="30"
> description="Account password" />
> <column name="externalId" required="false" type="VARCHAR" size="30"
> description="External Account Id" />
> </table>
>
> <table name="privilege" description="List of all Privileges"> <column
> name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" /> <column name="name" required="true" type="VARCHAR"

> size="50" description="Name of Privilege" />
> <column name="namepsace" required="true" type="VARCHAR" size="200"
> description="Namespace the privilege resides in" />
> </table>
>
> <table name="account_priv_ref" description="Maps Accounts to Available

> Privileges" /> <column name="account" type="INTEGER" required="true"
> primaryKey="true" />
> <column name="privilege" type="INTEGER" required="true"
> primaryKey="true" />
> <foreign-key foreignTable="account">
> <reference local="account" foreign="id"/>
> </foreign-key>
> <foreign-key foreignTable="privilege">
> <reference local="privilege" foreign="id"/>
> </foreign-key>
> </table>
>
> </database>
>
> Thanks,
>
> Matt


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

Re: [propel] Many-to-Many Relationship Problem

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-12 12:20:37 PDT
Message Hans,

Your description exactly describes my problem. The manual and examples
say it should work but I wanted to make sure I wasn't doing something
wrong.

Thanks for your help,

Matt

On Apr 12, 2004, at 14:53, Hans Lellelid wrote:

> Hi Matt,
>
> Yes, I believe this is a known issue (and in the bug tracker for me to
> tackle). I believe the error you got had something to do with lack of
> indexes on the fkey constraints, correct? This seems to be a
> mysql/innodb
> issue -- well, not an issue, just a difference between mysql and other
> dbs
> that use fkeys. This should be no problem to fix, since we have
> individual templates for all the db systems. I just haven't done it
> yet
> :) I think there's even some code on the dev list.... I'll try to get
> this done ASAP.
>
> If I'm wrong about the problem, let me know.
>
> Thanks,
> Hans
>
>> Hello,
>>
>> I have never used Foreign Keys before and on Saturday I found a
>> problem. I'm not sure if there is a problem in propel or maybe I
>> missed
>> something in my schema file. The schema is attached below.
>>
>> I created the first query after seeing a working example in the mysql
>> manual.
>>
>> The following CREATE TABLE works:
>> CREATE TABLE account_priv_ref(
>>
>> account INTEGER NOT NULL ,
>>
>> privilege INTEGER NOT NULL ,
>>
>> PRIMARY KEY(account,privilege),
>> INDEX(account),
>> FOREIGN KEY (account) REFERENCES account (id),
>> INDEX(privilege),
>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>
>> This query was created by the propel build file.
>> This CREATE TABLE fails: (errno: 150 [foreign-key problem])
>> CREATE TABLE account_priv_ref(
>>
>> account INTEGER NOT NULL ,
>>
>> privilege INTEGER NOT NULL ,
>>
>> PRIMARY KEY(account,privilege),
>> FOREIGN KEY (account) REFERENCES account (id),
>> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>>
>> Here are the other two related tables:
>> CREATE TABLE account(
>>
>> id INTEGER NOT NULL ,
>>
>> firstName VARCHAR(30) NOT NULL ,
>>
>> lastName VARCHAR(30) NOT NULL ,
>>
>> email VARCHAR(100) ,
>>
>> username VARCHAR(30) NOT NULL ,
>>
>> password VARCHAR(30) NOT NULL ,
>>
>> externalId VARCHAR(30) ,
>>
>> PRIMARY KEY(id)) Type=InnoDB;
>>
>> CREATE TABLE privilege(
>>
>> id INTEGER NOT NULL ,
>>
>> name VARCHAR(50) NOT NULL ,
>>
>> namepsace VARCHAR(200) NOT NULL ,
>>
>> PRIMARY KEY(id)) Type=InnoDB;
>>
>> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.
>>
>> Schema
>> ---
>> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
>> <!DOCTYPE database SYSTEM "../dtd/database.dtd">
>>
>> <database name="athena" defaultIdMethod="native">
>> <table name="account" description="User Table">
>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>> description="id" />
>> <column name="firstName" required="true" type="VARCHAR" size="30"
>> description="First Name of User" />
>> <column name="lastName" required="true" type="VARCHAR" size="30"
>> description="Last Name of User" />
>> <column name="email" required="false" type="VARCHAR" size="100"
>> description="Email Address of User" />
>> <column name="username" required="true" type="VARCHAR" size="30"
>> description="Account username" />
>> <column name="password" required="true" type="VARCHAR" size="30"
>> description="Account password" />
>> <column name="externalId" required="false" type="VARCHAR" size="30"
>> description="External Account Id" />
>> </table>
>>
>> <table name="privilege" description="List of all Privileges">
>> <column name="id" required="true" primaryKey="true" type="INTEGER"
>> description="id" />
>> <column name="name" required="true" type="VARCHAR" size="50"
>> description="Name of Privilege" />
>> <column name="namepsace" required="true" type="VARCHAR" size="200"
>> description="Namespace the privilege resides in" />
>> </table>
>>
>> <table name="account_priv_ref" description="Maps Accounts to Available
>> Privileges" />
>> <column name="account" type="INTEGER" required="true"
>> primaryKey="true"
>> />
>> <column name="privilege" type="INTEGER" required="true"
>> primaryKey="true" />
>> <foreign-key foreignTable="account">
>> <reference local="account" foreign="id"/>
>> </foreign-key>
>> <foreign-key foreignTable="privilege">
>> <reference local="privilege" foreign="id"/>
>> </foreign-key>
>> </table>
>>
>> </database>
>>
>> Thanks,
>>
>> Matt
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

RE: [propel] Many-to-Many Relationship Problem

Reply

Author "Denny H dot Shimkoski" <dhs at hamfish dot org>
Full name "Denny H dot Shimkoski" <dhs at hamfish dot org>
Date 2004-04-12 12:15:32 PDT
Message OK... obviously I'm an idiot. :)
I just sent an email complaining about this very thing
RIGHT AFTER I read through it.

<sigh>

-----Original Message-----
From: Hans Lellelid [mailto:hans at velum dot net]
Sent: Monday, April 12, 2004 2:54 PM
To: users at propel dot tigris dot org
Subject: Re: [propel] Many-to-Many Relationship Problem


Hi Matt,

Yes, I believe this is a known issue (and in the bug tracker for me to
tackle). I believe the error you got had something to do with lack of
indexes on the fkey constraints, correct? This seems to be a
mysql/innodb issue -- well, not an issue, just a difference between
mysql and other dbs that use fkeys. This should be no problem to fix,
since we have individual templates for all the db systems. I just
haven't done it yet
:) I think there's even some code on the dev list.... I'll try to get
this done ASAP.

If I'm wrong about the problem, let me know.

Thanks,
Hans

> Hello,
>
> I have never used Foreign Keys before and on Saturday I found a
> problem. I'm not sure if there is a problem in propel or maybe I
> missed something in my schema file. The schema is attached below.
>
> I created the first query after seeing a working example in the mysql
> manual.
>
> The following CREATE TABLE works:
> CREATE TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> INDEX(account),
> FOREIGN KEY (account) REFERENCES account (id),
> INDEX(privilege),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> This query was created by the propel build file.
> This CREATE TABLE fails: (errno: 150 [foreign-key problem]) CREATE
> TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> FOREIGN KEY (account) REFERENCES account (id),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> Here are the other two related tables:
> CREATE TABLE account(
>
> id INTEGER NOT NULL ,
>
> firstName VARCHAR(30) NOT NULL ,
>
> lastName VARCHAR(30) NOT NULL ,
>
> email VARCHAR(100) ,
>
> username VARCHAR(30) NOT NULL ,
>
> password VARCHAR(30) NOT NULL ,
>
> externalId VARCHAR(30) ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> CREATE TABLE privilege(
>
> id INTEGER NOT NULL ,
>
> name VARCHAR(50) NOT NULL ,
>
> namepsace VARCHAR(200) NOT NULL ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.
>
> Schema
> ---
> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> <!DOCTYPE
> database SYSTEM "../dtd/database.dtd">
>
> <database name="athena" defaultIdMethod="native">
> <table name="account" description="User Table">
> <column name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" /> <column name="firstName" required="true"
> type="VARCHAR" size="30" description="First Name of User" />
> <column name="lastName" required="true" type="VARCHAR" size="30"
> description="Last Name of User" />
> <column name="email" required="false" type="VARCHAR" size="100"
> description="Email Address of User" />
> <column name="username" required="true" type="VARCHAR" size="30"
> description="Account username" />
> <column name="password" required="true" type="VARCHAR" size="30"
> description="Account password" />
> <column name="externalId" required="false" type="VARCHAR" size="30"
> description="External Account Id" />
> </table>
>
> <table name="privilege" description="List of all Privileges"> <column
> name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" /> <column name="name" required="true" type="VARCHAR"

> size="50" description="Name of Privilege" />
> <column name="namepsace" required="true" type="VARCHAR" size="200"
> description="Namespace the privilege resides in" />
> </table>
>
> <table name="account_priv_ref" description="Maps Accounts to Available

> Privileges" /> <column name="account" type="INTEGER" required="true"
> primaryKey="true" />
> <column name="privilege" type="INTEGER" required="true"
> primaryKey="true" />
> <foreign-key foreignTable="account">
> <reference local="account" foreign="id"/>
> </foreign-key>
> <foreign-key foreignTable="privilege">
> <reference local="privilege" foreign="id"/>
> </foreign-key>
> </table>
>
> </database>
>
> Thanks,
>
> Matt


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

Re: [propel] Many-to-Many Relationship Problem

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-12 11:53:52 PDT
Message Hi Matt,

Yes, I believe this is a known issue (and in the bug tracker for me to
tackle). I believe the error you got had something to do with lack of
indexes on the fkey constraints, correct? This seems to be a mysql/innodb
issue -- well, not an issue, just a difference between mysql and other dbs
that use fkeys. This should be no problem to fix, since we have
individual templates for all the db systems. I just haven't done it yet
:) I think there's even some code on the dev list.... I'll try to get
this done ASAP.

If I'm wrong about the problem, let me know.

Thanks,
Hans

> Hello,
>
> I have never used Foreign Keys before and on Saturday I found a
> problem. I'm not sure if there is a problem in propel or maybe I missed
> something in my schema file. The schema is attached below.
>
> I created the first query after seeing a working example in the mysql
> manual.
>
> The following CREATE TABLE works:
> CREATE TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> INDEX(account),
> FOREIGN KEY (account) REFERENCES account (id),
> INDEX(privilege),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> This query was created by the propel build file.
> This CREATE TABLE fails: (errno: 150 [foreign-key problem])
> CREATE TABLE account_priv_ref(
>
> account INTEGER NOT NULL ,
>
> privilege INTEGER NOT NULL ,
>
> PRIMARY KEY(account,privilege),
> FOREIGN KEY (account) REFERENCES account (id),
> FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;
>
> Here are the other two related tables:
> CREATE TABLE account(
>
> id INTEGER NOT NULL ,
>
> firstName VARCHAR(30) NOT NULL ,
>
> lastName VARCHAR(30) NOT NULL ,
>
> email VARCHAR(100) ,
>
> username VARCHAR(30) NOT NULL ,
>
> password VARCHAR(30) NOT NULL ,
>
> externalId VARCHAR(30) ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> CREATE TABLE privilege(
>
> id INTEGER NOT NULL ,
>
> name VARCHAR(50) NOT NULL ,
>
> namepsace VARCHAR(200) NOT NULL ,
>
> PRIMARY KEY(id)) Type=InnoDB;
>
> Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.
>
> Schema
> ---
> <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
> <!DOCTYPE database SYSTEM "../dtd/database.dtd">
>
> <database name="athena" defaultIdMethod="native">
> <table name="account" description="User Table">
> <column name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" />
> <column name="firstName" required="true" type="VARCHAR" size="30"
> description="First Name of User" />
> <column name="lastName" required="true" type="VARCHAR" size="30"
> description="Last Name of User" />
> <column name="email" required="false" type="VARCHAR" size="100"
> description="Email Address of User" />
> <column name="username" required="true" type="VARCHAR" size="30"
> description="Account username" />
> <column name="password" required="true" type="VARCHAR" size="30"
> description="Account password" />
> <column name="externalId" required="false" type="VARCHAR" size="30"
> description="External Account Id" />
> </table>
>
> <table name="privilege" description="List of all Privileges">
> <column name="id" required="true" primaryKey="true" type="INTEGER"
> description="id" />
> <column name="name" required="true" type="VARCHAR" size="50"
> description="Name of Privilege" />
> <column name="namepsace" required="true" type="VARCHAR" size="200"
> description="Namespace the privilege resides in" />
> </table>
>
> <table name="account_priv_ref" description="Maps Accounts to Available
> Privileges" />
> <column name="account" type="INTEGER" required="true" primaryKey="true"
> />
> <column name="privilege" type="INTEGER" required="true"
> primaryKey="true" />
> <foreign-key foreignTable="account">
> <reference local="account" foreign="id"/>
> </foreign-key>
> <foreign-key foreignTable="privilege">
> <reference local="privilege" foreign="id"/>
> </foreign-key>
> </table>
>
> </database>
>
> Thanks,
>
> Matt


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

[propel] Many-to-Many Relationship Problem

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-12 10:30:16 PDT
Message Hello,

I have never used Foreign Keys before and on Saturday I found a
problem. I'm not sure if there is a problem in propel or maybe I missed
something in my schema file. The schema is attached below.

I created the first query after seeing a working example in the mysql
manual.

The following CREATE TABLE works:
CREATE TABLE account_priv_ref(

    account INTEGER NOT NULL ,

    privilege INTEGER NOT NULL ,

     PRIMARY KEY(account,privilege),
     INDEX(account),
     FOREIGN KEY (account) REFERENCES account (id),
     INDEX(privilege),
     FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;

This query was created by the propel build file.
This CREATE TABLE fails: (errno: 150 [foreign-key problem])
CREATE TABLE account_priv_ref(

    account INTEGER NOT NULL ,

    privilege INTEGER NOT NULL ,

     PRIMARY KEY(account,privilege),
     FOREIGN KEY (account) REFERENCES account (id),
     FOREIGN KEY (privilege) REFERENCES privilege (id)) Type=InnoDB;

Here are the other two related tables:
CREATE TABLE account(

    id INTEGER NOT NULL ,

    firstName VARCHAR(30) NOT NULL ,

    lastName VARCHAR(30) NOT NULL ,

    email VARCHAR(100) ,

    username VARCHAR(30) NOT NULL ,

    password VARCHAR(30) NOT NULL ,

    externalId VARCHAR(30) ,

     PRIMARY KEY(id)) Type=InnoDB;

CREATE TABLE privilege(

    id INTEGER NOT NULL ,

    name VARCHAR(50) NOT NULL ,

    namepsace VARCHAR(200) NOT NULL ,

     PRIMARY KEY(id)) Type=InnoDB;

Mysql version is 4.1.0-max-alpha, binary distribution, on freebsd 4.9.

Schema
---
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<!DOCTYPE database SYSTEM "../dtd/database.dtd">

<database name="athena" defaultIdMethod="native">
<table name="account" description="User Table">
<column name="id" required="true" primaryKey="true" type="INTEGER"
description="id" />
<column name="firstName" required="true" type="VARCHAR" size="30"
description="First Name of User" />
<column name="lastName" required="true" type="VARCHAR" size="30"
description="Last Name of User" />
<column name="email" required="false" type="VARCHAR" size="100"
description="Email Address of User" />
<column name="username" required="true" type="VARCHAR" size="30"
description="Account username" />
<column name="password" required="true" type="VARCHAR" size="30"
description="Account password" />
<column name="externalId" required="false" type="VARCHAR" size="30"
description="External Account Id" />
</table>

<table name="privilege" description="List of all Privileges">
<column name="id" required="true" primaryKey="true" type="INTEGER"
description="id" />
<column name="name" required="true" type="VARCHAR" size="50"
description="Name of Privilege" />
<column name="namepsace" required="true" type="VARCHAR" size="200"
description="Namespace the privilege resides in" />
</table>

<table name="account_priv_ref" description="Maps Accounts to Available
Privileges" />
<column name="account" type="INTEGER" required="true" primaryKey="true"
/>
<column name="privilege" type="INTEGER" required="true"
primaryKey="true" />
<foreign-key foreignTable="account">
<reference local="account" foreign="id"/>
</foreign-key>
<foreign-key foreignTable="privilege">
<reference local="privilege" foreign="id"/>
</foreign-key>
</table>

</database>

Thanks,

Matt
Attachments

Re: [propel] Syntax error in the manual.

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-09 12:05:36 PDT
Message Hi Matt,

Thanks for the fix!

The website update is still manual -- I just update the checkout in the
docs/user_guide directory. It'd probably be good to eventually update
this at some point, but for now I dont mind just jumping in there &
updating it.

(BTW -- I did update it after your fix.)

Hans

Matthew B.Hershberger wrote:

> Hans,
>
> The typo has been fixed in cvs. When and/or how is the website updated?
>
> Thanks,
>
> Matt
>
> On Apr 9, 2004, at 10:20 AM, Hans Lellelid wrote:
>
>> Hi Matt--
>>
>>> I found a syntax error, a very trivial mistake, in the manual under
>>> Many to Many relationships there is a missing `>' after `<table'. If
>>> I check out the cvs can I update the manual as I find errors or
>>> should I just report them via the mailing list?
>>
>>
>> Absolutely feel free to fix any errors you find (in manual or
>> elsewhere). It's also fine to submit bug reports, but in many cases
>> it might be just faster to fix it yourself & commit. All we ask is
>> that if you are fixing something that might break existing code
>> (obviously doesn't apply to the manual), send out a note to
>> dev at propel dot tigris dot org first to double check. But really -- a very
>> relaxed policy on committing to CVS. It is, afterall, CVS and we can
>> rollback if something breaks. Mostly we're just really grateful for
>> any help & have no desire to make it difficult or beaurocratic for
>> people to help out.
>>
>> I granted you 'developer' role on the project so that you can commit
>> to the CVS repository.
>>
>> Thanks!
>> Hans
>>
>>
>>
>> --------------------​--------------------​--------------------​---------
>> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
>> For additional commands, e-mail: users-help at propel dot tigris dot org
>>
>>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

Re: [propel] Syntax error in the manual.

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-09 09:46:16 PDT
Message Hans,

The typo has been fixed in cvs. When and/or how is the website updated?

Thanks,

Matt

On Apr 9, 2004, at 10:20 AM, Hans Lellelid wrote:

> Hi Matt--
>
>> I found a syntax error, a very trivial mistake, in the manual under
>> Many to Many relationships there is a missing `>' after `<table'. If
>> I check out the cvs can I update the manual as I find errors or
>> should I just report them via the mailing list?
>
> Absolutely feel free to fix any errors you find (in manual or
> elsewhere). It's also fine to submit bug reports, but in many cases
> it might be just faster to fix it yourself & commit. All we ask is
> that if you are fixing something that might break existing code
> (obviously doesn't apply to the manual), send out a note to
> dev at propel dot tigris dot org first to double check. But really -- a very
> relaxed policy on committing to CVS. It is, afterall, CVS and we can
> rollback if something breaks. Mostly we're just really grateful for
> any help & have no desire to make it difficult or beaurocratic for
> people to help out.
>
> I granted you 'developer' role on the project so that you can commit
> to the CVS repository.
>
> Thanks!
> Hans
>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
> For additional commands, e-mail: users-help at propel dot tigris dot org
>
>


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

Re: [propel] Syntax error in the manual.

Reply

Author hlellelid
Full name Hans Lellelid
Date 2004-04-09 07:20:30 PDT
Message Hi Matt--

> I found a syntax error, a very trivial mistake, in the manual under
> Many to Many relationships there is a missing `>' after `<table'. If I
> check out the cvs can I update the manual as I find errors or should I
> just report them via the mailing list?

Absolutely feel free to fix any errors you find (in manual or
elsewhere). It's also fine to submit bug reports, but in many cases it
might be just faster to fix it yourself & commit. All we ask is that if
you are fixing something that might break existing code (obviously
doesn't apply to the manual), send out a note to dev at propel dot tigris dot org
first to double check. But really -- a very relaxed policy on
committing to CVS. It is, afterall, CVS and we can rollback if
something breaks. Mostly we're just really grateful for any help & have
no desire to make it difficult or beaurocratic for people to help out.

I granted you 'developer' role on the project so that you can commit to
the CVS repository.

Thanks!
Hans



--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org

[propel] Syntax error in the manual.

Reply

Author matthewh
Full name Matthew Hershberger
Date 2004-04-09 07:10:13 PDT
Message I found a syntax error, a very trivial mistake, in the manual under
Many to Many relationships there is a missing `>' after `<table'. If I
check out the cvs can I update the manual as I find errors or should I
just report them via the mailing list?


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@pr​opel.tigris.org
For additional commands, e-mail: users-help at propel dot tigris dot org
Messages per page: