Jeremy, you never cease to amaze. Thank you so much.
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sequel-talk+unsubscr...@googlegroups.com.
To post to this gro
On Thursday, December 1, 2016 at 6:45:31 PM UTC-8, Elanor Riley wrote:
>
> Hello!
> I am writing an app that is limited to work within an existing database,
> therefore some of the table names may collide. Is there a way to assign a
> table prefix so that migrations / etc create, for example *new
Hello!
I am writing an app that is limited to work within an existing database,
therefore some of the table names may collide. Is there a way to assign a
table prefix so that migrations / etc create, for example *newapp_users*
rather than *users*?
For example, active record has table_name_prefi
Sequel 4.41.0 has been released!
= New Features
* Dataset#with_* methods have been added as equivalents for a
few Dataset#*= methods, but instead of modifying the receiver, they
return a modified copy, similar to the dataset query methods.
Specific methods added:
with_extend :: Extends c
