Thank you, I could cleary understand what you think.
> I also don't expect there to be a lot of changes around additional
> refactorings or database support, but if it gets to be a problem we can
> always change our approach.
Yes, we can change anytime.
--
Yasuo Honda
On Thu, Sep 25, 2008 at 1:22 AM, Voxland, Nathan
<nvoxland@...> wrote:
> That was one issue I was thinking about as I was going through every
> page adding SQLite support :)
>
> The reason I am leaning to keeping the full list of database
> compatibility on each refactoring page is because I think it keeps the
> documentation cleaner and keeps compatibility in the minds of developers
> and users.
>
> I think for sure we need to specify any incompatibilities on each
> refactoring page because trying to list and reference back to
> incompatible refactorings from a single page would get word-y and
> difficult to follow. We could pull out the "No Issues" databases, but I
> like having them in because then as I am documenting them it makes me
> think back to "is there really no issues for this database on this
> refactoring?" and there is a placeholder for people to add issues as
> they find them that keeps the database list in a consistent order from
> page to page.
>
> I also don't expect there to be a lot of changes around additional
> refactorings or database support, but if it gets to be a problem we can
> always change our approach.
>
> Nathan
>
> -----Original Message-----
> From: Yasuo HONDA [mailto:yahonda@...]
> Sent: Tuesday, September 23, 2008 8:42 PM
> To: liquibase-documentation@...
> Subject: Re: [Liquibase-documentation] dbms attribute in changeset
>
> Thank you for your quick update.
>
> It is good idea to refer supported database page as you did.
>
> My second concern is that as support database grows,
> we need to update and each refactoring page by page add new database
> compatibility.
>
> By separating refactorings and database compatibility page
> this issue can be solved. but if new refactorings are added similar
> issues will be occured...
>
> Anyway, thank you for your update.
>
> --
> Yasuo Honda
>
> On Wed, Sep 24, 2008 at 12:40 AM, Voxland, Nathan
> <nvoxland@...> wrote:
>> You are right. The full list of options may only exist In the code,
>> currently. Maybe we should add the type name to supported database
> page
>> so we can just manage it there and refer back to it as needed. Take a
>> look at how I changed it and let me know what you think.
>>
>> Nathan
>>
>> -----Original Message-----
>> From: Yasuo HONDA [mailto:yahonda@...]
>> Sent: Tuesday, September 23, 2008 10:28 AM
>> To: liquibase-documentation@...
>> Subject: [Liquibase-documentation] dbms attribute in changeset
>>
>> Hi,
>>
>> LiquiBase core 1.8 supports SQLite database.
>> In changeset, dbms attribute also supports "sqlite" ?
>>
>> http://www.liquibase.org/manual/changeset
>>
>>>> The type of a database which that changeSet is to be used for. When
>> the migration step is running, it checks the database type against
> this
>> attribute. Currently, the legal values include "db2", "derby",
> "hsqldb",
>> "h2", "mssql", "mysql", "oracle", "postgresql", "cache", and
> "firebird"
>>
>> I try to find which values supported, I could not find exact
>> information.
>>
>> Thanks in advance,
>>
>> --
>> Yasuo HONDA
>>
>>
> ------------------------------------------------------------------------
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Liquibase-documentation mailing list
>> Liquibase-documentation@...
>> https://lists.sourceforge.net/lists/listinfo/liquibase-documentation
>>
>>
> ------------------------------------------------------------------------
> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Liquibase-documentation mailing list
>> Liquibase-documentation@...
>> https://lists.sourceforge.net/lists/listinfo/liquibase-documentation
>>
>>
>
> ------------------------------------------------------------------------
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-documentation mailing list
> Liquibase-documentation@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-documentation
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Liquibase-documentation mailing list
> Liquibase-documentation@...
> https://lists.sourceforge.net/lists/listinfo/liquibase-documentation
>
>
|