Re: [Lift] derby
Derby has inferior support for binary data types (32k limit) and has a couple of other issues that I can't remember off the top of my head. On Thu, Nov 26, 2009 at 1:54 PM, jlist9 jli...@gmail.com wrote: Hi David, Would you care to elaborate in what way Derby is inferior? I understand H2 is probably faster as speed is one of its main design goals. Does Derby have any other issues? Are there any potential issues with using H2 for production? Thanks, Jack Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
I see. Thanks Derek. On Fri, Nov 27, 2009 at 8:42 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Derby has inferior support for binary data types (32k limit) and has a couple of other issues that I can't remember off the top of my head. On Thu, Nov 26, 2009 at 1:54 PM, jlist9 jli...@gmail.com wrote: Hi David, Would you care to elaborate in what way Derby is inferior? I understand H2 is probably faster as speed is one of its main design goals. Does Derby have any other issues? Are there any potential issues with using H2 for production? Thanks, Jack Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
Anything larger than 32k should probably be a BLOB anyway (for which Derby has full support). However, I'm going to take a look at H2 anyway. On Fri, Nov 27, 2009 at 11:42 AM, Derek Chen-Becker dchenbec...@gmail.com wrote: Derby has inferior support for binary data types (32k limit) and has a couple of other issues that I can't remember off the top of my head. On Thu, Nov 26, 2009 at 1:54 PM, jlist9 jli...@gmail.com wrote: Would you care to elaborate in what way Derby is inferior? I understand H2 is probably faster as speed is one of its main design goals. Does Derby have any other issues? Are there any potential issues with using H2 for production? Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- Family photographs are a critical legacy for ourselves and our descendants. Protect that legacy with a digital backup and recovery plan. Join the photo preservation advocacy Facebook group: http://www.facebook.com/home.php?ref=logo#/group.php?gid=148274709288 -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
On Thu, Nov 26, 2009 at 12:54 PM, jlist9 jli...@gmail.com wrote: Hi David, Would you care to elaborate in what way Derby is inferior? I understand H2 is probably faster as speed is one of its main design goals. Does Derby have any other issues? I needed to do a lot more work arounds for Derby in Mapper/Schemifier... H2 was more true to the SQL spec. I have had a few instances of Derby databases getting corrupt during unclean shutdowns... that's never happened with H2. Are there any potential issues with using H2 for production? Thanks, Jack Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
That's good to know. Thanks! On Fri, Nov 27, 2009 at 10:50 AM, David Pollak feeder.of.the.be...@gmail.com wrote: I needed to do a lot more work arounds for Derby in Mapper/Schemifier... H2 was more true to the SQL spec. I have had a few instances of Derby databases getting corrupt during unclean shutdowns... that's never happened with H2. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
On Wed, Nov 25, 2009 at 10:48 PM, jack jack.wid...@gmail.com wrote: Could somebody point me to a quickstart or tutorial about how to use Derby with Lift? Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.comliftweb%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/liftweb?hl=en. -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Re: [Lift] derby
Hi David, Would you care to elaborate in what way Derby is inferior? I understand H2 is probably faster as speed is one of its main design goals. Does Derby have any other issues? Are there any potential issues with using H2 for production? Thanks, Jack Derby is inferior in every way to H2 (another open source pure Java relational database). If you're building something for production, Postgresql is your best choice. If you need a simple database that needs no separate process and just works H2 is your best choice. -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
[Lift] derby
Could somebody point me to a quickstart or tutorial about how to use Derby with Lift? -- You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
[Lift] Derby Identity column DDL and SQL insert scripts
All Using Derby and have hit an issue when running some SQL scripts to insert data into a fresh mapper DB created by schemifier. Specifically when inserting records with the id column I get a violation: Error: Attempt to modify an identity column 'ID'. SQLState: 42Z23 ErrorCode: -1 i.e data can't be inserted into this column which is not helpful when this id is the primary key and foreign key on another table. Derby does support auto-incremented sequence values as *default only* when you are not providing values as opposed to always providing auto- incremented sequence values which you are not allowed to specify your own values. The difference is GENERATED BY DEFAULT AS IDENTITY instead of GENERATED ALWAYS AS IDENTITY. To this end it looks like net.liftweb.mapper.DerbyDriver.scala needs updating from def integerIndexColumnType = INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY def longIndexColumnType = BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY to def integerIndexColumnType = INTEGER NOT NULL GENERATED BY DEFAULT AS IDENITY def longIndexColumnType = BIGINT NOT NULL GENERATED BY DEFAULT AS IDENTITY Hope this helps -- Ewan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Derby ij quickstart?
I added derby.drda.startNetworkServer=true to derby.settings as mentioned on http://liftweb.net/index.php/Cheat_Sheet, and I figured out to add the dependency for derbynet.jar in Maven. I can connect with DbVisualize and see various system tables, but I can't see any tables lift created. Not sure what the problem is, but I'd actually rather just connect with ij to take a quick peek. I can't quite get that working: java -cp derbytools-10.2.2.0.jar org.apache.derby.tools.ij ij version 10.2 ij connect 'jdbc:derby://localhost:1527/lift_example'; ERROR 08001: No suitable driver found for jdbc:derby://localhost:1527/lift_example Can someone point out what I'm doing wrong? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
