Hi,
is C where supposed to work with a scalar (or list) reference? If yes,
then it's broken.
Note: The following code is for MySQL.
CREATE TABLE confirmation (
id INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
user INT UNSIGNED,
FOREIGN KEY (user) REFERENCES user
Matt S Trout wrote:
While I remember: can everybody with an active branch off -current sing
out and tell us
(1) what it's designed for
source-handle branch - replaces all -result_source with a
(schema,source_name) tuple.
``This module removes fixed link between Rows/ResultSets and the
Matt S Trout wrote:
While I remember: can everybody with an active branch off -current sing
out and tell us
(1) what it's designed for
(2) where it's up to
(3) when you expect it to be ready for audit before merge to -current
Note: If it's already ready for audit, kick me and I'll try
--- Carl Franks [EMAIL PROTECTED] wrote:
On 20/12/06, Matt S Trout [EMAIL PROTECTED]
wrote:
While I remember: can everybody with an active
branch off -current sing
out and tell us
columns_info_for
(1) what it's designed for
Detailed column specs (as much as each database will
Hi folks, thanks for your precious time,
I am citing this old message by Matt,, thanks again for DBIx:Class(
http://www.mail-archive.com/dbix-class@lists.rawmode.org/msg00081.html
), and i am wondering if someone has good news or knows something that
could help me to downgrade
On 12/21/06, John Napiorkowski [EMAIL PROTECTED] wrote:
How is you new 'columns_info_for' method accessed?
Right now columns_info_for (the method, as opposed to the branch, but
I'm assuming the branch extends the same basic concepts the current
method has...) is in a deprecated state. In
On 21/12/06, John Napiorkowski [EMAIL PROTECTED] wrote:
--- Carl Franks [EMAIL PROTECTED] wrote:
On 20/12/06, Matt S Trout [EMAIL PROTECTED]
wrote:
While I remember: can everybody with an active
branch off -current sing
out and tell us
columns_info_for
(1) what it's designed for
