Re: [Liquibase-user] Conventions
I added a link to a Best Practices page on the site's sidebar that had been built up a couple weeks ago but never actually liked to. http://www.liquibase.org/bestpractices Anything you or anyone else think should be documented in there can be. To answer some of your questions that I don't think are on the best practices page currently: - You can't put your (main) create database statement in your changelog file because liquibase needs a database in which to save its databasechangelog table in. It would be fine to create database statements for other databases, but you need to have at least one existing before liquibase can run - Creating users is fine in liqubase, but you do need to have one pre-existing to connect to the database with for liquibase to read the databasechangelog file for - In general, I think that all database changes that you can do should be stored in your changelog files so they will be applied to all databases. Permissions, datatabases, and users have some limitations due to liqubase bootstrapping issues, but they should be included if possible Liquibase does run fine off existing tables. It is best if you have a standard or set schema to start working from, but there are many features available to make the transition easier (generateChangeLog command, diff commands, tableExists precondition, etc). Let us know if you have any other questions. Nathan -Original Message- From: Joelle Tegwen [mailto:tegwe...@umn.edu] Sent: Monday, February 02, 2009 11:58 AM To: liquibase-user@lists.sourceforge.net Subject: [Liquibase-user] Conventions This is not really a how to question but more of a should I question. Do you put your create database, create users, set permissions in the configuration files? Is this a best practice? If you do: Do you then create a separate changeset.properties and changeset.xml for those specific items? How does liquibase work with existing tables in them? Are there any side effects to beware of? Is there anything I'm missing here? I love this product BTW. I'm not a database person primarily and managing the differences between 3 servers has really been a major source of problems and headaches for me. This is a sanity saver. :) My only wish is that I had found this earlier when I was searching on database version control. For some reason you don't come up on google. Thanks Joelle -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user
Re: [Liquibase-user] Oracle anonymous blocks and triggers
Thanks Damian!! Adding splitStatements=false as you suggested works both when executing an anonymous block using sql and when creating a trigger using sqlFile. Cheers, Tom -Original Message- From: Damian Gołda [mailto:damian.go...@gmail.com] Sent: Friday, January 30, 2009 1:38 PM To: liquibase-user@lists.sourceforge.net Subject: Re: [Liquibase-user] Oracle anonymous blocks and triggers Hi I suppose the reason s that sql and sqlFile split whole text to many statements using ; as delimiter. So try: - set splitStatements attribute to false, or - use createProcedure element (yes, I used createProcedure for plsql functions and packages). -- Damian 2009/1/30 Starr, Thomas tst...@cobaltgroup.com: Hi folks - I need to confirm whether one should be able to use either update or updateSQL where sqlFile= in the change log references a file containing anonymous plsql block (or a trigger). Also whether update and updateSQL should both work with the same anonymous block (or trigger) instead enclosed in sql/sql tags in the change log. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user
Re: [Liquibase-user] Search Optimization (was Conventions)
All good keywords - the one I was personally looking at when I accidentally came across Liquibase was Database configuration management, database deployment, database migration and database refactor/refactoring To improve said SEO profile there are a few things thhat help: 1) Getting linked iks the big one and your bang on we need more! The more places that point to liquibase the higher we'll be ranked on Google based on the search terms that hit. 2) Getting these terms on the front page as frequently as reasonable along with pseudonims will help improve the profile as well. 3) Long DNS records make a decent difference as well, never just renew for a year, renew for the maximum they give you the option for (3?). 4) More articles will help too by providing more links back to the site and more users coming to it and more bookmarks etc etc. I will help with (4) through the old blog and JavaLobby. Paul - Original Message From: Voxland, Nathan nvoxl...@intelligentinsites.com To: liquibase-user@lists.sourceforge.net Sent: Monday, 2 February, 2009 19:10:36 Subject: [Liquibase-user] Search Optimization (was Conventions) I wish people would find us more too... Is there any chance that there are any search engine optimization experts out there interested in helping us out to improve our visibility? In my unbiased option, LiquiBase is something that all database projects need to be using, and not enough people are :) Also, what types of search queries do you think we should target or optimize for? I'm not exactly sure what to call the area liquibase hits. Is it database version control? Is it database refactoring? Is it database change management? Something else? Probably the biggest thing we need to do is get more incoming links. I keep planning on spending more time pushing and writing about liquibase, but I keep pushing it off in favor of feature enhancements. Nathan -Original Message- From: Joelle Tegwen [mailto:tegwe...@umn.edu] Sent: Monday, February 02, 2009 11:58 AM To: liquibase-user@lists.sourceforge.net Subject: [Liquibase-user] Conventions This is not really a how to question but more of a should I question. Do you put your create database, create users, set permissions in the configuration files? Is this a best practice? If you do: Do you then create a separate changeset.properties and changeset.xml for those specific items? How does liquibase work with existing tables in them? Are there any side effects to beware of? Is there anything I'm missing here? I love this product BTW. I'm not a database person primarily and managing the differences between 3 servers has really been a major source of problems and headaches for me. This is a sanity saver. :) My only wish is that I had found this earlier when I was searching on database version control. For some reason you don't come up on google. Thanks Joelle -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com ___ Liquibase-user mailing list Liquibase-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/liquibase-user
