comment on

Some ideas:

1. CREATE TABLE foo will fail when a table foo exists
2. DBI should report the error
3. deploy should fail
SELECT 42 AS result FROM foo should fail when no table and no view named foo exists
You can enumerate the tables in the database, and you can enumerate the columns in the table.

Testing one table is usually not sufficient, as you usually have more than one table, and you may add or remove tables as development goes on. The same applies to columns in the tables. Ideally, deploy() should handle all these cases.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re: DBIC & deploy by afoken
in thread DBIC & deploy by pileofrogs

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.